lvresize and XFS, was: default file system

Eric Sandeen sandeen at redhat.com
Thu Feb 27 23:02:30 UTC 2014


On 2/27/14, 4:40 PM, Chris Murphy wrote:
> 
> On Feb 27, 2014, at 3:32 PM, Chris Murphy <lists at colorremedies.com> wrote:
> 
>>
>> On Feb 27, 2014, at 3:02 PM, Jochen Schmitt <Jochen at herr-schmitt.de> wrote:
>>
>>> On Thu, Feb 27, 2014 at 04:08:46PM -0500, James Wilson Harshaw IV wrote:
>>>> A question I have is XFS worth it?
>>>
>>> I have done some testing with RHEL 7 Beta which use XFS as a default file system.
>>>
>>> I have to recorgnize, that the -r switch of the lvresize command doesn't cooperate
>>> with xfs in oppoiste of ext4.
>>
>> Where you growing or shrinking the fs, and was it mounted at the time, and what error did you get? XFS doesn't support shrink, and only can be grown online. I'm pretty sure lvresize -r supports xfs_growfs via fsadm.
> 
> worksforme
> 
> Starting with a 10TB XFS volume, 5TB x 5 disk VG.
> 
> 
> # lvresize -r -v --size 15T VG/LV
>     Finding volume group VG
>     Executing: fsadm --verbose check /dev/VG/LV
> fsadm: "xfs" filesystem found on "/dev/mapper/VG-LV"
> fsadm: Skipping filesystem check for device "/dev/mapper/VG-LV" as the filesystem is mounted on /mnt
>     fsadm failed: 3

<snip>

> However, I don't know what "fsadm failed: 3" means.

fsadm.sh:

        if detect_mounted ; then
                verbose "Skipping filesystem check for device \"$VOLUME\" as the filesystem is mounted on $MOUNTED";
                cleanup 3
        fi

...
cleanup() {
...
        exit ${1:-1}
}

the script exits with error "3" meaning, well, "3," I guess, when the fs is mounted.  Not the nicest error reporting IMHO :)

-Eric



More information about the devel mailing list