View Single Post
Old 05-27-2019, 05:46 PM   #4
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
I definitely started to notice it with the Forma, and I just chalked it up to Nickel being a tad heavy-handed about handling /mnt/onboard during USBMS sessions, and/or the fsck version they ship being stupid about clearing the dirty bit.

I never actually ever encountered a real FS corruption, and a proper, recent fsck run basically only ever clears the dirty bit, so I've just stopped wondering about it ;p.

EDIT: A quick glance at my dmesg shows that, yep, also seeing it on the H2O. Except in that case I *may* have had something to do with it, because I *did* actually unmount onboard like a savage a couple times ;p.

Code:
[73769.000316] FAT-fs (sde): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Code:
fsck.vfat /dev/sde
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
Perform changes ? (y/n) y
/dev/sde: 15178 files, 485455/829227 clusters

Last edited by NiLuJe; 05-27-2019 at 06:31 PM.
NiLuJe is offline   Reply With Quote