Re: Correct fsck behavior on boot

[Edward Shishkin <edward.shishkin@gmail.com>]

Anders Aagaard wrote:
> Alexander Lyamin wrote:
>> Why one have to worry about cleanness   of a  _journaled_ fs ?
>> Its seems like immediate return on -a is intended behavior.
>
> I suspect it is, I'm just making sure I have something to fire back
> with when a gentoo developer complains about my patch here:
>
> http://bugs.gentoo.org/show_bug.cgi?id=237393

Would you please maintain this issue in Gentoo? I was sure that reiser4
is not checked after every incorrect umount, whereas people shrink their
root partitions, format them with other file systems, etc.. and this is sad.

Thanks,
Edward.

>>
>> On Thu, Sep 11, 2008 at 3:26 PM, Anders Aagaard <aagaande@gmail.com
>> <mailto:aagaande@gmail.com>> wrote:
>>
>>     Hi
>>
>>     What's the correct options to pass to reiser4.fsck on boot to get it
>>     to check the filesystem when it's not marked as clean?
>>
>>     reiser4 fsck does implement -a, but it seems to return right away,
>>     including when the filesystem wasn't unmounted cleanly.  Is the
>>     filesystem integrity still secured by hash'es, so skipping fsck is
>>     intentional?
>>     --check --fix seems a tad bit excessive on every boot.
>>
>>     Anders Aagaard
>>
>>
>>
>> -- 
>> connecting the dots
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe
> reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>