lvresize and XFS, was: default file system

Chris Murphy lists at colorremedies.com
Fri Feb 28 13:37:57 UTC 2014


On Feb 28, 2014, at 1:33 AM, Zdenek Kabelac <zkabelac at redhat.com> wrote:


>>>     fsadm failed: 3
> 

> man fsadm
> 
> DIAGNOSTICS
>       On  successful completion, the status code is 0.  A status code of 2 indicates the operation was interrupted by the user.  A
>       status code of 3 indicates the requested check operation could not be performed because the filesystem is mounted  and  does
>       not support an online fsck(8).  A status code of 1 is used for other failures.

Yeah but did fsadm fail? No, as a whole its operation succeeded. Can we say fsadm failed to run fsck? I guess that's one way to look at it, but then it failed to understand it shouldn't request a check operation on XFS in the first place.

Chris Murphy



More information about the devel mailing list