Thread: Glo Glo and Win 8.1
View Single Post
Old 05-07-2015, 10:48 PM   #18
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
No other OSes will even notice the dirty bit. They don't create it, they don't know how to find it, they don't use it, they don't delete it.

I don't worry my other OSes are messing up, but if the world would move on to a modern fs as the default cross-platform fs, then maybe we could use something like ext4.

linux will automatically fsck filesystems at regular intervals. Windows instead decides to warn you with angry popups about nothing.
Most of the times when I boot up, I get bootup logs telling me that orphaned inodes are being cleared up. That would be fsck at work. I don't have to do anything (it is a kernel/initramfs default) and it happens quite fast (seconds) on my nice modern fs.

I have nothing wrong on principle with telling the user his/her fs has a corruption issue, but Windows freaking out when a drive is not unmounted via the designated flush-data-and-unmount feature is unacceptable. It is just as effective and only a little more logical than warning about possible corruption as a Tuesday special.
By which I mean to say, naturally if you demand a filesystem check at random intervals it will sometimes pay off. But the dirty bit doesn't really help that process.
And it is chkdsk (fsck for Windows) that has fixed problems, not the dirty bit.
eschwartz is offline   Reply With Quote