<p dir="ltr">So far my small of research shows it isn't that big of a problem. We should look more into it thought.<br>
On Feb 27, 2014 5:41 PM, "Chris Murphy" <<a href="mailto:lists@colorremedies.com">lists@colorremedies.com</a>> wrote:<br>
><br>
><br>
> On Feb 27, 2014, at 3:32 PM, Chris Murphy <<a href="mailto:lists@colorremedies.com">lists@colorremedies.com</a>> wrote:<br>
><br>
> ><br>
> > On Feb 27, 2014, at 3:02 PM, Jochen Schmitt <<a href="mailto:Jochen@herr-schmitt.de">Jochen@herr-schmitt.de</a>> wrote:<br>
> ><br>
> >> On Thu, Feb 27, 2014 at 04:08:46PM -0500, James Wilson Harshaw IV wrote:<br>
> >>> A question I have is XFS worth it?<br>
> >><br>
> >> I have done some testing with RHEL 7 Beta which use XFS as a default file system.<br>
> >><br>
> >> I have to recorgnize, that the -r switch of the lvresize command doesn't cooperate<br>
> >> with xfs in oppoiste of ext4.<br>
> ><br>
> > 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.<br>
><br>
> worksforme<br>
><br>
> Starting with a 10TB XFS volume, 5TB x 5 disk VG.<br>
><br>
><br>
> # lvresize -r -v --size 15T VG/LV<br>
> Finding volume group VG<br>
> Executing: fsadm --verbose check /dev/VG/LV<br>
> fsadm: "xfs" filesystem found on "/dev/mapper/VG-LV"<br>
> fsadm: Skipping filesystem check for device "/dev/mapper/VG-LV" as the filesystem is mounted on /mnt<br>
> fsadm failed: 3<br>
> Archiving volume group "VG" metadata (seqno 2).<br>
> Extending logical volume LV to 15.00 TiB<br>
> Loading VG-LV table (253:0)<br>
> Suspending VG-LV (253:0) with device flush<br>
> Resuming VG-LV (253:0)<br>
> Creating volume group backup "/etc/lvm/backup/VG" (seqno 3).<br>
> Logical volume LV successfully resized<br>
> Executing: fsadm --verbose resize /dev/VG/LV 16106127360K<br>
> fsadm: "xfs" filesystem found on "/dev/mapper/VG-LV"<br>
> fsadm: Device "/dev/mapper/VG-LV" size is 16492674416640 bytes<br>
> fsadm: Parsing xfs_info "/mnt"<br>
> fsadm: Resizing Xfs mounted on "/mnt" to fill device "/dev/mapper/VG-LV"<br>
> fsadm: Executing xfs_growfs /mnt<br>
> meta-data=/dev/mapper/VG-LV isize=256 agcount=10, agsize=268435455 blks<br>
> = sectsz=512 attr=2<br>
> data = bsize=4096 blocks=2684354550, imaxpct=5<br>
> = sunit=0 swidth=0 blks<br>
> naming =version 2 bsize=4096 ascii-ci=0<br>
> log =internal bsize=4096 blocks=521728, version=2<br>
> = sectsz=512 sunit=0 blks, lazy-count=1<br>
> realtime =none extsz=4096 blocks=0, rtextents=0<br>
> data blocks changed from 2684354550 to 4026531825<br>
><br>
> # df -h<br>
> Filesystem Size Used Avail Use% Mounted on<br>
> /dev/mapper/VG-LV 15T 33M 15T 1% /mnt<br>
><br>
><br>
> However, I don't know what "fsadm failed: 3" means.<br>
><br>
><br>
> Chris Murphy<br>
> --<br>
> devel mailing list<br>
> <a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/devel">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
> Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct">http://fedoraproject.org/code-of-conduct</a></p>