On 4/15/13 11:45 AM, Dan McGrath wrote:
> Jan,
>
> I got a chance to sit down and dig a little bit deeper into
> `fsck.xfs`. Here is what I discovered.
>
> The "(a|A|y|p)" options in the XFS script appear to be nothing more
> than the expected `fsck` options that imply automated checks (as is
> clearly implied by the use of AUTO). While I have yet to specifically
> test the capitalized "A", my guess is that it matches the "-A" options
> from fsck(8) for when the system is going through the fstab. The
> syntax itself appears to assume that the dev name is the last param
> (as indicated by the argc/$#, which gets eval'd into the DEV
> variable).
>
> After doing some tests with a hacked up version of the `fsck.xfs`
> script, it would appear that the generic `fsck` script calls each
> script in order and passes it some parameters to test, since if I pass
> `fsck` some random/btrfsck switches:
>
> # fsck --repair /dev/storage/lv_btrfs
>
> I get an error back from `fsck.ext4`:
>
> fsck from util-linux 2.20.1
> fsck.ext4: invalid option -- 'e'
2 things; from the fsck manpage:
fsck [-sAVRTMNP] [-C [fd]] [-t fstype] [filesys...] [--] [fs-specific-options]
so I think you need:
fsck -- --repair /dev/storage/lv_btrfs
But the other issues seems to be that fsck & blkid are autodetecting
the device as ext4, not btrfs; a separate issue.
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
