Correct fsck behavior on boot

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

 



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
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux File System Development]     [Linux BTRFS]     [Linux NFS]     [Linux Filesystems]     [Ext4 Filesystem]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Resources]

  Powered by Linux