<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Ok, thank you all for the responses. Makes sense.</p>
<p><br>
</p>
<p>E.</p>
<p><br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">Elliot Holden
706-231-9776
<a class="moz-txt-link-abbreviated" href="mailto:elliot@elliotmywebguy.com">elliot@elliotmywebguy.com</a>
<a class="moz-txt-link-freetext" href="http://www.elliotmywebguy.com">http://www.elliotmywebguy.com</a></pre>
<div class="moz-cite-prefix">On 5/8/17 10:44 AM, Kyle Brieden wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0c988a26d618858b09acd60ccd6f6ca7@txmoose.com">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 type="cite">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.<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ale mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ale@ale.org">Ale@ale.org</a>
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a>
</pre>
</blockquote>
<br>
</body>
</html>