Thread: Firmware 4.31.19086
View Single Post
Old 04-06-2022, 01:16 AM   #651
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by DNSB View Post
Interesting. Since Kobo updated the fat filesystem check (dosfsck aka fsck.fat) to v4.1 2017-01-24 several firmware revisions back, I haven't seen the dirty bit set popping up the Windows file system check dialog. When Kobo updates to v4.2, that will clear the dirty bit on run regardless of whether it was set or not.
Quote:
Originally Posted by DNSB View Post
What I managed to get with a kepub open during connect was a read-only mount. Again, I couldn't reliably duplicate it.
The issue seems to be that sometimes the kepub renderer is not closing a file if a kepub is open when the device is connected to the PC. That means that sometimes the file system is not unmounted cleanly and the dirty bit is set. Then sometimes when you disconnect the device, the filesystem is mounted read only on the device.

The problem for working it out is the "sometimes". For me, it didn't happen all the time. And each of the "sometimes" above didn't happen every time. I think I was seeing about 50% for the dirty bit but less than 10% for the read-only. I assume there was something in the books, or the user configuration, or something like how long between turning a page and plugging in, or when the last sleep was (that commits the reading session) or some other absurd sounding thing going on. And my devices all behaved a little differently. I could never figure it out. Which I think you saw elsewhere.
davidfor is offline   Reply With Quote