<html><head></head><body>Oops, yes, I've even used it that way.<br>
<br>
Also,<br>
LVM is helpful here, because you can migrate a running LV to a new disk in the VG, then delete the original disk, then grow the LV - all without downtime.<br>
-Adam<br><br><div class="gmail_quote">On February 3, 2016 1:07:29 AM CST, Wolfgang Bumiller <w.bumiller@proxmox.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> On February 2, 2016 at 8:07 PM Adam Thompson <athompso@athompso.net> wrote:<br /> <br /> On 16-02-02 11:24 AM, Gilberto Nunes wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> Hi<br /><br /> And what if I work with BTRFS inside the VM???<br /> The FS where VM image lay could be any other FS... Currently, I am use <br /> GlusterFS + XFS.<br /> I need LVM or BRTFS inside the VM, in order to resize disk partition...<br /> And I am between LVM or BRTFS....<br /></blockquote> <br /> Only if you need to do *online* resizes (without unmounting the <br /> filesystem). If you can live with unmounting the filesystem, plain old <br /> ext3 (and ext4) can do what you need. Of course, if it's the root <br /> filesystem you need to resize, the only way to unmount it is to
shut <br /> down the VM and reboot it in single-user mode. I think you might need <br /> to boot off a CD to resize the root fs, can't remember if there's a way <br /> around it.<br /></blockquote><br />Actually resize2fs works on mounted file systems as long as you're only<br />growing it and not shrinking it, including the root filesystem.<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><<<br /></blockquote></blockquote><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> On February 2, 2016 at 4:38 PM Gilberto Nunes <gilberto.nunes32@gmail.com> wrote:<br /> That's other doubt... I will lose data if I do it with parted resizepart???<br /></blockquote><br />No, but naturally you should make a backup
just in case, especially when<br />you do this the first time.<br />Of course there are some limitations when you need online resizing without<br />downtime. Then you can only grow a partition without moving it. In other<br />words you can only resize a partition if there's physical free space directly<br />after it. (Most of the time this is the case since you usually have the<br />boot partition first and then the root and maybe a home or data partition,<br />and most of the time that last one is the one you want to resize ;-) )<br />Eg. with [boot, root, home] after resizing the physical disk you end up with<br />[boot, root, home, <frees space>], so you can only resize the home partition.<br />If you can afford down time you can also use parted to move partitions so that<br />you can resize any of them. This however takes a lot longer and is a bit<br />more risky, so in this case you should _always_ make a backup even if you know<br />what you're doing.<br /><br
/></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>