Quote:
Originally Posted by PeterT
But you're the only Kindle user reporting this issue......
|
Joined here to say I am affected by this, too. Or by something somewhat similar, at least.
I was lucky to find this thread easily, since having to disconnect and reconnect the device for
every book copied is not a proper experience. Thsnks yorikk for your analysis. At least I know there is something quite broken with Kindle firmware.
I may be facing something different, though.
udisk2 was already being used, but it isn't adding a flush option, it gets mounted with:
Code:
rw,nosuid,nodev,noexec,relatime,sync,uid=<uid>,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro,uhelper=udisks2
The calibre version (3.39.1, from Debian) is prior to the utime fix, but the kernel version is also prior to 4.19.50, so this system [em]shouldn't[/em] be affected. And in fact, the one-liner
Code:
python -c "p = '/run/media/kovid/Kindle/driveinfo.calibre'; f = open(p, 'r+b'); import os; os.fsync(f.fileno());"
doesn't disconnect it (NB: "import os" is missing in the code), yet something is disconnecting it after every calibre book transfer. Maybe not fsync related, after all, since commenting the two fsync() calls (plus restarting calibre, obviously) didn't help.