Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with editing files on mounted device #80

Open
dretechtips opened this issue Sep 21, 2020 · 3 comments
Open

Issue with editing files on mounted device #80

dretechtips opened this issue Sep 21, 2020 · 3 comments

Comments

@dretechtips
Copy link

What the Issues?

I am unable to edit files on any android device I've mounted. However, I'm able to create and delete files without any issue. Sometime when I initiate a file transfer the file is created on the mounted device, however the content is empty. Thus, I can deductively reason that the issue is limited to the inability for simple-mtpfs to edit created files.

How to replicate the issue?

  1. Mount the device
  2. Go to the directory
  3. touch filename.txt
  4. echo file content > filename.txt

Expected behavior

No output

Actual behavior

echo: write error: input/output error

PC Config

Build: https://aur.archlinux.org/packages/simple-mtpfs-git/
Distro: Arch Linux
Kernel: 5.8.9-arch2-1

Android Device Config

Oneplus 8 128GB

@dgulotta
Copy link

dgulotta commented Oct 13, 2020

I am having the same issue. I am using Gentoo Linux with kernel 5.4.38-gentoo and a Moto G6. The issue started with commit 2bcc455; everything worked fine before that.

@GOKOP
Copy link

GOKOP commented Aug 3, 2021

I have the same problem. What's more interesting, the device is useless after that error happens. I can read from it fine before it, but after the first failed write any file operation at all hangs the program performing it. Furthermore, after unmounting the device it can't be mounted again (LIBMNT PANIC: trying to dump stack of a NULL device!) until I disconnect my phone and connect it again.

@l29ah
Copy link

l29ah commented Feb 26, 2022

Thank you, reverting 2bcc455 fixed the problem for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants