Filesystem check forced, lack of information, and takes an houre.

[finalbeta]

Today I had enother forced file system check when booting.
hda6/7 get a progress bar when checking.

My +-300 gig ext3 partition hdb5 doesn't get a progress bar. Meaning I'm watching a blinking _ for about 45 minutes.

PS: what's up with that time anyway? I have no simple way of getting around that check (after a crash), so when I just needed to quicly grab a file before I left, I ended up being delayed 1 houre. That's just not exeptable...

[Carey Underwood (cwillu)]

Is there any references to ext2 in your /etc/fstab? Do you use the ext2/3 driver for windows to access that partition? Had you mounted it by hand anywhere?

Sounds like it wasn't mounted as ext3, or the journal was damaged for some reason. The delay you speak of is a major reason for using journaling in ext3. Without the journal, ext3 is just ext2, which requires a repair process that's proportional to the size of your drive (people used to complain about it taking too long back even when drives were only a few hundred megs).

Lack of feedback is a problem though; I think there's a spec on that too.

[finalbeta (j-greenhouse)]

Thanks for responding.

I am using the ext2 driver for windows. I never really considered the consequences of that, that it reverts my partition to ext2. (that is pretty stupid of me)

Seems this is my own fault and this can be closed.

PS: I upgraded to edgy, removed file checking at X boots, and now it's less of an issue.