diff options
| author | Richard W.M. Jones <rjones@redhat.com> | 2010-11-27 18:48:48 +0000 |
|---|---|---|
| committer | Richard W.M. Jones <rjones@redhat.com> | 2010-11-27 18:52:51 +0000 |
| commit | 6f09e4774ce64a15424a2601df10326d764cc7f7 (patch) | |
| tree | ee07670b0017e7ee5f56a4594705428a8878c981 /tools | |
| parent | 866a6a0fa5124a06918f84b7db28f831ab6e4495 (diff) | |
| download | libguestfs-6f09e4774ce64a15424a2601df10326d764cc7f7.tar.gz libguestfs-6f09e4774ce64a15424a2601df10326d764cc7f7.tar.xz libguestfs-6f09e4774ce64a15424a2601df10326d764cc7f7.zip | |
docs: Fix small inaccuracies in virt-resize(1).
Diffstat (limited to 'tools')
| -rwxr-xr-x | tools/virt-resize | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/tools/virt-resize b/tools/virt-resize index 1e8a6c7b..76abb1e7 100755 --- a/tools/virt-resize +++ b/tools/virt-resize @@ -172,9 +172,7 @@ PV, then if virt-resize knows how, it will resize the contents, the equivalent of calling a command such as L<pvresize(8)>, L<resize2fs(8)> or L<ntfsresize(8)>. However virt-resize does not know how to resize some filesystems, so you would have to online -resize them after booting the guest. And virt-resize also does not -resize anything inside an LVM PV, it just resizes the PV itself and -leaves the user to resize any LVs inside that PV as desired. +resize them after booting the guest. Other options are covered below. @@ -361,9 +359,9 @@ Windows will check the disk. =item * -LVM PVs (physical volumes). However virt-resize does I<not> -resize anything inside the PV. The user will have to resize -LVs as desired. +LVM PVs (physical volumes). virt-resize does not usually resize +anything inside the PV, but see the C<--LV-expand> option. The user +could also resize LVs as desired after boot. =back |