<div dir="auto">XFS does NOT support shrinking. It supports exabytes of storage and will happily expand to any size up to it's limit. <div dir="auto"><br></div><div dir="auto">Apparently, XFS was designed by/for hoarders. :-)</div></div><div class="gmail_extra"><br><div class="gmail_quote">On May 8, 2017 10:45 AM, "Kyle Brieden" <<a href="mailto:kyle@txmoose.com">kyle@txmoose.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey Elliot,<br>
<br>
I've been doing it this way for years. I know for srure that it is safe to extend an ext# FS online. I believe XFS is safe to extend online, as well. The lvextend -r flag just calls "resize2fs" (or tune2fs? I honestly can't recall which it is off hand right now...) for you. For what it's worth, I've extended filesystems while they were being written to this way to avoid having a filesystem fill up in the middle of a long-running process and breaking the process.<br>
<br>
Sizing a filesystem down, on the other hand, should never be done online. But extending a filesystem online is typically safe.<br>
<br>
I also recently discovered the hard way that either XFS or ZFS (I can't recall which, as I use both but very, VERY little) can be extended, but not shrunk. As it, the spec for the FS was actively written to not allow shrinking. Struck me as odd, but I guess there's a logical reason there.<br>
<br>
---<br>
Very respectfully,<br>
Kyle Brieden<br>
<br>
On 08-05-2017 10:31, Elliot Holden wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I found out you can extend the filesystem while extending the lvm<br>
simultaneously. So it does not have to be in 2 separate commands.<br>
Using the -r option or --resizefs with lvextend will do the trick.<br>
This way you don't have to unmount the filesystem, extend the<br>
filesystem (with xfs_growfs) and then remount the filesystem. Here is<br>
the syntax.<br>
<br>
[elliot@newton ~]$ sudo lvextend -l +100%FREE -r /dev/rhel/home<br>
<br>
<br>
Does any see an issue with doing this type of modification while the<br>
filesystem is still mounted? Does anyone know if the filesystem gets<br>
unmounted and remounted during this command while using -r ? Just in<br>
case some other process is writing to the filesystem at the same time.<br>
It's been brought to my attention by a member of my Perl group that<br>
you could potentially lose data this way. So I wanted to find out if<br>
there are any protections going on in the background while executing<br>
this command.<br>
<br>
<br>
Thanks<br>
<br>
<br>
E.</blockquote>
<br>______________________________<wbr>_________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/<wbr>listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/<wbr>listinfo</a><br>
<br></blockquote></div></div>