[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ext3 mounted fs still needs fscking after crash



Hi,

Thanks, Ted, for the help. Now I am sure that my fs isn't mounted as ext3,
because the has_journal feature is not present. When I use tune2fs -j
/dev/sda2, the flag appears, but after reboot it's gone. The silly thing
is that the output of mount is
/dev/sda2 on / type ext3 (rw)

Now, I didn't know that 2.4.10 was buggy, but I tried to upgrade as you
said. I applied the patches for 2.4.11-dontuse (interesting name...) and
then 2.4.12. But now the kernel won't compile because of
--------
balloc.c: In function `ext3_free_blocks':
balloc.c:432: warning: passing arg 1 of `DQUOT_FREE_BLOCK' from
incompatible pointer type
balloc.c:432: warning: passing arg 2 of `DQUOT_FREE_BLOCK' makes integer
from pointer without a cast
balloc.c:432: too many arguments to function `DQUOT_FREE_BLOCK'
balloc.c: In function `ext3_new_block':
balloc.c:571: warning: passing arg 1 of `DQUOT_ALLOC_BLOCK' from
incompatible pointer type
balloc.c:571: warning: passing arg 2 of `DQUOT_ALLOC_BLOCK' makes integer
from pointer without a cast
balloc.c:571: too many arguments to function `DQUOT_ALLOC_BLOCK'
--------

So I don't know what to do now... What version of the kernel should I
reinstall, so that I can apply a patch for ext3 and mount correctly?
There's still no patch against 2.4.12, is it?

Sorry if that sounds stupid, I'm quite lost in all those version numbers,
I must admit.

Thanks again in advance,
Pierric.





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]