View Single Post
Old 02-11-2022, 03:16 AM   #280
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
Quote:
Originally Posted by rashkae View Post
My only conclusion here, the Kobo had not finished unmounting the user partition before allowing the computer to mount it.
It's possible, it happened before.

Kobo uses lazy umounting, and "lazy" means it's not unmounted at all while still in use.

The result is filesystem inconsistency and perhaps includes Windows complaining about the filesystem.

I had a mod to detect this condition ( https://www.mobileread.com/forums/sh...d.php?t=263674 to display a happy or sad smiley face depending on umount status ) and try to detect the cause what is preventing the umount, but of course it's old and unmaintained and probably won't work, for current devices.

Back then it was the KEPUB Reader that prevented umount if you connected while reading the book, it was fine if you connected USB from the home menu.

Of course any addon can also block it, if it has anything in /mnt/onboard open.
frostschutz is offline   Reply With Quote