OK, I think I see what you were saying there (having a bit of trouble with the grammar; my German is so rusty as to be useless, but learning it while I did gave me an appreciation for how hard it is to write/speak in a language I didn't grow up with, so I'm not complaining about it; I just mention it by way of apology for any remaining misunderstandings). You keep the VGs themselves small, to minimize administrative/maintenance task times. The situations in which you're looking to resize an LV are right after increasing the size of the VG the LV belongs to. This makes complete sense, and I feel a bit silly for not thinking of such a setup myself.<br><br><div class="gmail_quote">On Sat, Nov 29, 2014, 11:20 Cesar Peschiera <<a href="mailto:brain@click.com.py">brain@click.com.py</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div bgcolor="#ffffff">
<div><font face="Arial">Hi Daniel</font></div>
<div> </div>
<div><font face="Arial">Thanks for your clarification, it is good know it,
and please let me to do some comments:</font></div>
<div> </div>
<div><font face="Arial">About of do to grow the max the VD of the VM: as a
administration strategy, if my hard disks don't have all the space
occupied with a Physical Volume, will be very easy and online expand any thing
of LVM which is desired, as also can be util if you want to use such space free
for other things out of LVM.</font></div>
<div> </div>
<div><font face="Arial">Moreover, as a administration strategy, if my DRBD
resource has a space very limited, the verification of DRBD storages will take
less time to complete (talking in hours of time), and when more later i want do
grow the DRBD resource for any need (that always i can do it), entails to
that after will be need grow the Physical Volume and the Volume Group that is
within of the DRBD resource, then finally, i will gain time for that DRBD
completes the verification of his storages that are executed automatic and
periodically if is that it is limited the space of these resources.</font></div>
<div> </div>
<div><font face="Arial">Unfortunately, the times of delay for that finish
the tasks of verifications of storages replicated or shared always was a topic
of study and strategy important for his administrators, due to that also the VMs
are using these same hard disks at the same time that a verification is in
progress, and obviously it can be more critical talking in speed terms when a
data base depend of these hard drives.</font></div>
<div> </div>
<div><font face="Arial">And finally, I know that the all manufacturers of
hard drives tell us about of the percent of error in writes that have his hard
drives, and is for it (as also for other reasons), that any decent RAID
controller have the option of verify these units.</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">So in conclusion, and talking in general mode, as
are needed that the systems to make these tasks:<br>1) The backup of the
VMs.<br>2) The verification of the storages replicated.<br>3) The verification
of the HDDs.<br>4) All these tasks must be do in online mode, but none at the
same time for avoid degradation of yield.</font></div>
<div> </div>
<div><font face="Arial">It is for it that i need reduce the times of this
verifications to the max possible, and also so i need to have the data and
storages as small as possible, whether they are in a RAID Controller, as in LVM,
DRBD, Gluster, Ceph, hardware storage or any kind of storage that
exists.</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">Best regards</font></div></div><div bgcolor="#ffffff">
<div><font face="Arial">Cesar</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial"></font> </div>
</div><div bgcolor="#ffffff"><blockquote style="BORDER-LEFT:#000000 2px solid;PADDING-LEFT:5px;PADDING-RIGHT:0px;MARGIN-LEFT:5px;MARGIN-RIGHT:0px" dir="ltr">
<div style="FONT:10pt arial">----- Original Message ----- </div>
<div style="FONT:10pt arial;BACKGROUND:#e4e4e4"><b>From:</b>
<a title="danhunsaker@gmail.com" href="mailto:danhunsaker@gmail.com" target="_blank">Daniel
Hunsaker</a> </div>
</blockquote></div><div bgcolor="#ffffff"><blockquote style="BORDER-LEFT:#000000 2px solid;PADDING-LEFT:5px;PADDING-RIGHT:0px;MARGIN-LEFT:5px;MARGIN-RIGHT:0px" dir="ltr"><div style="FONT:10pt arial"><b>To:</b> <a title="brain@click.com.py" href="mailto:brain@click.com.py" target="_blank">Cesar Peschiera</a> ; <a title="aderumier@odiso.com" href="mailto:aderumier@odiso.com" target="_blank">Alexandre
DERUMIER</a> ; <a title="pve-devel@pve.proxmox.com" href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a> </div>
<div style="FONT:10pt arial"><b>Sent:</b> Saturday, November 29, 2014 8:43
AM</div>
<div style="FONT:10pt arial"><b>Subject:</b> Re: [pve-devel] Error between
PVE and LVM</div>
<div><br></div>It'll be some time before such options can be added to the
underlying Proxmox API.<br><br>As to your comments about the resize not
showing in the GUI even with qm resize, that isn't quite true. Let's say you'd
resize your LV normally using `lvextend -L 100G`. I understand you'd prefer to
use `100%` here, but just bear with my example for the moment and pretend
you'd use `100G`. Changing that to `qm resize 100G` would not only resize the
LV to 100 GB, but also tell QEMU about the new size, which would in turn
update the GUI. That's because the qm command hooks into the same code the GUI
uses to make the changes it makes. So switching to `qm resize` will give you
the VM/GUI update at the cost of using % sizes (for now).<br><br>I still don't
understand what benefit you'd get from increasing a single VM's LV to the full
VG size. No other LV would then be able to grow within that VG. The only setup
I can imagine that would avoid that problem is one where each LV has a
dedicated VG, which is to say, each VG only has a single LV. That setup seems
pretty inefficient to me, not really taking advantage of LVM's design
principles. But then, maybe I'm just missing something.<br><br>
<div class="gmail_quote">On Sat, Nov 29, 2014, 00:37 Cesar Peschiera <<a href="mailto:brain@click.com.py" target="_blank">brain@click.com.py</a>> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote"><u></u>
<div bgcolor="#ffffff">
<div><font face="Arial">Hi Daniel</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">As the moderns Windows systems have the options of
grow or shrink the partitions of his HDDs online, add such features to the
PVE GUI will be very pleasant.</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">And if is possible also add the a option of "resize to
the max allowed" (the space available in his Volume group) , will be
fantastic.</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">Best regards</font></div></div>
<div bgcolor="#ffffff">
<div><font face="Arial">Cesar</font></div></div>
<div bgcolor="#ffffff">
<blockquote style="BORDER-LEFT:#000000 2px solid;PADDING-LEFT:5px;PADDING-RIGHT:0px;MARGIN-LEFT:5px;MARGIN-RIGHT:0px" dir="ltr">
<div style="FONT:10pt arial">----- Original Message ----- </div>
<div style="FONT:10pt arial;BACKGROUND:#e4e4e4"><b>From:</b> <a title="danhunsaker@gmail.com" href="mailto:danhunsaker@gmail.com" target="_blank">Daniel Hunsaker</a> </div>
<div style="FONT:10pt arial"><b>To:</b> <a title="aderumier@odiso.com" href="mailto:aderumier@odiso.com" target="_blank">Alexandre DERUMIER</a>
</div></blockquote></div>
<div bgcolor="#ffffff">
<blockquote style="BORDER-LEFT:#000000 2px solid;PADDING-LEFT:5px;PADDING-RIGHT:0px;MARGIN-LEFT:5px;MARGIN-RIGHT:0px" dir="ltr">
<div style="FONT:10pt arial"><b>Cc:</b> <a title="pve-devel@pve.proxmox.com" href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a> ; <a title="brain@click.com.py" href="mailto:brain@click.com.py" target="_blank">Cesar Peschiera</a> </div>
<div style="FONT:10pt arial"><b>Sent:</b> Friday, November 28, 2014 3:55
AM</div>
<div style="FONT:10pt arial"><b>Subject:</b> Re: [pve-devel] Error
between PVE and LVM</div>
<div><br></div>The only difference between lvresize and lvextend is that
lvresize supports shrinking the volume as well as growing it. My comments
aren't questions so much as observations on a patch series I'm planning to
create and submit that will allow shrinking volumes as well as expanding
them. Probably roll the max-free option in there as well if it hasn't been
added already by then, though I wonder at the utility of such an
operation, since you could only use it on one lv per vg.<br><br>
<div class="gmail_quote">On Thu, Nov 27, 2014, 23:49 Alexandre DERUMIER
<<a href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a>> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Sorry, but I'm a bit lost in all the
discussion.<br><br>are your questions (both daniel and cesar) about
shrinking ? or extend ?<br><br>(I don't have used lvm since a long
time, don't known the difference between lvresize and
lvextend).<br><br>@cesar, I don't understand why since the begin of this
discus, you resize manually the lvm disk.<br>(If the need is to do it
command line, use qm resize, it'll extend the lvm volume and tell to
qemu the new size)<br><br><br><br><br>----- Mail original
-----<br><br>De: "Daniel Hunsaker" <<a href="mailto:danhunsaker@gmail.com" target="_blank">danhunsaker@gmail.com</a>><br>À: "Alexandre DERUMIER"
<<a href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a>>, "Cesar Peschiera" <<a href="mailto:brain@click.com.py" target="_blank">brain@click.com.py</a>><br>Cc: <a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a><br>Envoyé: Vendredi 28
Novembre 2014 06:32:15<br>Objet: Re: [pve-devel] Error between PVE and
LVM<br><br>Ah, good, it does support +size. In that case, simply
swapping `lvresize` into the code in place of `lvextend` (along with
properly handling -size to convert it to an absolute size for the
command) would add shrinking support to LVM storage. Just need to
further explore the other storage plugins' resize options to get
shrinking for them as well. Makes the patches a bit simpler.<br><br>And
yes, I always forget about `qm`. It's quite a bit simpler than
`pvesh`.<br><br><br>On Thu, Nov 27, 2014, 22:11 Alexandre DERUMIER <
<a href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a> > wrote:<br><br><br>>>But
for this moment, i have two questions:<br>>>1) Do I have any
simpler option to grow my LV(that is the HDD of the VM)
by<br>>>CLI?<br>>>2) If the answer is correct, what exactly
should i execute?<br><br>all the gui feature are available with cli,
with "qm" command.<br><br><br><br>#qm resize <vmid> <disk>
<size><br><br>#man qm<br>qm resize <vmid> <disk>
<size> [OPTIONS]<br><br>Extend volume size.<br><br><vmid>
integer (1 - N)<br><br>The (unique) ID of the VM.<br><br><disk>
(ide0 | ide1 | ide2 | ide3 | sata0 | sata1 | sata2 | sata3 |<br>sata4 |
sata5 | scsi0 | scsi1 | scsi10 | scsi11 | scsi12 |<br>scsi13 | scsi2 |
scsi3 | scsi4 | scsi5 | scsi6 | scsi7 | scsi8<br>| scsi9 | virtio0 |
virtio1 | virtio10 | virtio11 | virtio12 |<br>virtio13 | virtio14 |
virtio15 | virtio2 | virtio3 | virtio4 |<br>virtio5 | virtio6 | virtio7
| virtio8 | virtio9)<br><br>The disk you want to
resize.<br><br><size> \+?\d+(\.\d+)?[KMGT]?<br><br>The new size.
With the '+' sign the value is added to the<br>actual size of the volume
and without it, the value is taken<br>as an absolute one. Shrinking disk
size is not supported.<br><br>-digest string<br><br>Prevent changes if
current configuration file has different<br>SHA1 digest. This can be
used to prevent concurrent<br>modifications.<br><br>-skiplock
boolean<br><br>Ignore locks - only root is allowed to use this
option.<br><br><br>----- Mail original -----<br><br>De: "Cesar
Peschiera" < <a href="mailto:brain@click.com.py" target="_blank">brain@click.com.py</a> ><br>À: "Daniel Hunsaker" <
<a href="mailto:danhunsaker@gmail.com" target="_blank">danhunsaker@gmail.com</a> >, "Alexandre DERUMIER" <
<a href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a> ><br>Cc: <a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a><br>Envoyé: Jeudi 27 Novembre
2014 21:01:28<br>Objet: Re: [pve-devel] Error between PVE and
LVM<br><br>Thanks Daniel, your words are encouraging for the future of
PVE and for me.<br><br>But for this moment, i have two questions:<br>1)
Do I have any simpler option to grow my LV(that is the HDD of the VM)
by<br>CLI?<br>2) If the answer is correct, what exactly should i
execute?<br><br>Best regards<br>Cesar<br><br><br>----- Original Message
-----<br>From: Daniel Hunsaker<br>To: Alexandre DERUMIER ; Cesar
Peschiera<br>Cc: <a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a><br>Sent: Thursday, November
27, 2014 3:37 PM<br>Subject: Re: [pve-devel] Error between PVE and
LVM<br><br><br>If the GUI is resizing volumes, the API supports it,
which means you should<br>be able to use `pvesh` to do the operation in
one command, instead of using<br>the LVM commands and QEMU monitor
directly. It does only support specifying<br>the new size in bytes
(which it seems to convert to MiB before actually<br>using), but it's
still an option.<br><br>As for the "max available" option, I'd
personally find it more useful to<br>upgrade the API itself support the
full range of `lvresize -L` values (it<br>currently uses `lvextend`,
which means volumes cannot be reduced in size - a<br>fairly safe
approach in case the filesystem inside the VM hasn't been<br>reduced in
advance, but also a bit restrictive), or at least the largest<br>subset
we could also support for other storage plugins. I'll see
about<br>implementing that if nobody else gets to it
first.<br><br><br>On Thu, Nov 27, 2014, 09:15 Alexandre DERUMIER < <a href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a>
> wrote:<br><br>>>This process is correct when you use the GUI,
but when you have space<br>>>limited in the hard disk, and you
want to change some partitions by CLI,<br>>>where finally will be
working with the logical volumes, is when
starting<br>>>the<br>>>problem due that the VM not see the
change applied.<br><br>ah ok.<br><br>This is normal, you need to tell to
qemu what is the new size.<br>(This is what we are doing in the code :
vm_mon_cmd($vmid, "block_resize",<br>device => $deviceid, size =>
int($size)); )<br><br>if you manually upgrade the disk size,<br>you need
to use the monitor :<br><br>#block_resize device
size<br><br>ex:<br><br>#block_resize drive-virtio0
sizeinbytes<br><br><br><br><br><br><br><br>----- Mail original
-----<br><br>De: "Cesar Peschiera" < <a href="mailto:brain@click.com.py" target="_blank">brain@click.com.py</a>
><br>À: "Alexandre DERUMIER" < <a href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a>
><br>Cc: <a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a><br>Envoyé: Jeudi 27 Novembre
2014 17:00:37<br>Objet: Re: [pve-devel] Error between PVE and
LVM<br><br>Hi Alexandre<br><br>>This value correctly change after
resize ?<br>If, before change, the logical volume had a smaller
size.<br><br>>We first extend the lvm disk, then we tell to qemu the
new disk.<br>This process is correct when you use the GUI, but when you
have space<br>limited in the hard disk, and you want to change some
partitions by CLI,<br>where finally will be working with the logical
volumes, is when starting the<br>problem due that the VM not see the
change applied.<br><br>Please let me to do two suggestions:<br>- Maybe
will be better than PVE GUI have a option that say: "resize to
max<br>available", or something.<br>I guess that this first option would
be very good due to that the user will<br>not need calculate the space
available considering the space used in the<br>metadata of LVM.<br><br>-
Moreover, in previous versions of PVE, while that I could see
the<br>reflected changes into the VM, in the PVE GUI, when i see the
size of his<br>hard disk, it shows his old size, then i had that remove
the disk for re add<br>it, only of this manner i could see his new
size.<br><br>>What kind of disk do you use in your guest ? virtio ?
scsi ? ide ?<br>Virtio-block, moreover i have good references about
virtio-scsi, do you know<br>something about virtio-scsi for use it in
windows systems?<br><br>Many thanks again for your attention<br>Best
regards<br>Cesar<br><br><br>----- Original Message -----<br>From:
"Alexandre DERUMIER" < <a href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a> ><br>To: "Cesar Peschiera" <
<a href="mailto:brain@click.com.py" target="_blank">brain@click.com.py</a>
><br>Cc: < <a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a> ><br>Sent: Thursday,
November 27, 2014 6:35 AM<br>Subject: Re: [pve-devel] Error between PVE
and LVM<br><br><br>So,<br><br>>>shell# lvs<br>>>LV VG Attr
LSize Pool Origin Data% Move Log Copy% Convert<br>>>vm-100-disk-1
drbdvg2 -wi------ 30.00g<br><br>This value correctly change after resize
?<br><br><br><br>the resize code is here:<br><br>we first extend the lvm
disk, then we tell to qemu the new disk.<br><br>(What kind of disk do
you use in your guest ? virtio ? scsi ? ide
?)<br><br><br><br><br>/usr/share/perl5/PVE/ QemuServer.pm<br><br><br>sub
qemu_block_resize {<br>my ($vmid, $deviceid, $storecfg, $volid, $size) =
@_;<br><br>my $running = check_running($vmid);<br><br>return if
!PVE::Storage::volume_resize($ storecfg, $volid,
$size,<br>$running);<br><br>return if
!$running;<br><br>vm_mon_cmd($vmid, "block_resize", device =>
$deviceid, size
=><br>int($size));<br><br>}<br><br><br>/usr/share/perl5/PVE/Storage/
LVMPlugin.pm<br><br>sub volume_resize {<br>my ($class, $scfg, $storeid,
$volname, $size, $running) = @_;<br><br>$size = ($size/1024/1024) .
"M";<br><br>my $path = $class->path($scfg, $volname);<br>my $cmd =
['/sbin/lvextend', '-L', $size, $path];<br>run_command($cmd, errmsg
=> "error resizing volume '$path'");<br><br>return
1;<br>}<br><br>----- Mail original -----<br><br>De: "Cesar Peschiera"
< <a href="mailto:brain@click.com.py" target="_blank">brain@click.com.py</a> ><br>À: "Alexandre DERUMIER"
< <a href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a> ><br>Cc: <a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a><br>Envoyé: Jeudi 27 Novembre
2014 09:11:29<br>Objet: Re: [pve-devel] Error between PVE and
LVM<br><br>Hi Alexandre<br><br>Thanks for your attention, here my
answers and suggestions about of the<br>problem of your
customer:<br><br>>We have made no change since resize feature has
been implemented.<br>>Can you describe a little bit more the problem
on the guest side ?<br>>do you see disk size increase with
parted/fdisk ?<br>I see the new size (vm-100-disk-1) of the logical
volume by CLI, but it<br>isn't reflected into the VM.<br>In my case DRBD
is in a upper layer to the LV, but the concept of LVM is<br>applicable
for any Logical Volume in any kind of block device that Linux
can<br>recognise.<br>shell# lvs<br>LV VG Attr LSize Pool Origin Data%
Move Log Copy% Convert<br>vm-100-disk-1 drbdvg2 -wi------ 30.00g<br>data
pve -wi-ao--- 143.50g<br>root pve -wi-ao--- 20.00g<br>swap pve -wi-ao---
20.00g<br><br>>I have add a customer during a previous training
session, which have<br>>problem with raw lvm disk in vms,<br>I don't
have problems with the VMs (LVM or raw image file), only with the<br>LVM
resize by CLI.<br><br>>because of proxmox host scanning all lvm disks
on the host side. (Don't<br>>remember if it's have impact on
resize).<br>It don't have impact on resize, and it is necessary for that
LVM can manage<br>the changes online included (VM and host), that it is
my case.<br>Moreover, for my DRBD resources, i use this filter on the
lvm.conf file for<br>avoid scanning all lvm disks:<br><br>filter = [
"r|/dev/sdb1|", "r|/dev/sdc1|", "r|/dev/sdd1|",
"r|/dev/sde1|",<br>"r|/dev/disk/|", "r|/dev/block/|", "a/.*/"
]<br>Where:<br>a=accept (include) , and<br>r=reject (exclude) the scans
to speed startup.<br><br>>We have need to add a filter in lvm.conf on
the host, to exclude scan of<br>>vms lvm disk.<br>Sure, i use the
CLI<br><br>An additional note of IBM:<br>In the best practices, LVM as
block device is the mode more fast for get the<br>better performance in
reads and writes of disks.<br><br>Official Web page of IBM in "Best
practice: Use block devices for VM<br>storage":<br><a href="http://www-01.ibm.com/support/" target="_blank">http://www-01.ibm.com/support/</a>
knowledgecenter/linuxonibm/ liaat/liaatbpblock.htm<br><br>And finally,
my question:<br>Can be corrected my problem?<br><br>Best
regards<br>Cesar<br><br>----- Original Message -----<br>From: "Alexandre
DERUMIER" < <a href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a> ><br>To: "Cesar Peschiera" <
<a href="mailto:brain@click.com.py" target="_blank">brain@click.com.py</a>
><br>Cc: < <a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a> ><br>Sent: Thursday,
November 27, 2014 3:47 AM<br>Subject: Re: [pve-devel] Error between PVE
and LVM<br><br><br>Hi,<br><br>>>In previous versions of PVE, this
task was possible do it with much<br>>>easily.<br><br>We have made
no change since resize feature has been implemented.<br>Can you describe
a little bit more the problem on the guest side ?<br>do you see disk
size increase with parted/fdisk ?<br><br>Do you use raw lvm disk in your
vms ? or partitions on top of lvm ?<br>I have the LVM partition, and the
image of the virtual disk isn't on a file<br>system (as raw, qcow2, or
any other kind of file format), so my image disk<br>is a LVM as block
device.<br><br>I have add a customer during a previous training session,
which have problem<br>with raw lvm disk in vms,<br><br>because of
proxmox host scanning all lvm disks on the host side. (Don't<br>remember
if it's have impact on resize).<br><br>We have need to add a filter in
lvm.conf on the host, to exclude scan of vms<br>lvm disk.<br><br>-----
Mail original -----<br><br>De: "Cesar Peschiera" < <a href="mailto:brain@click.com.py" target="_blank">brain@click.com.py</a>
><br>À: <a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a><br>Envoyé: Jeudi 27 Novembre
2014 07:15:19<br>Objet: [pve-devel] Error between PVE and LVM<br><br>Hi
to the PVE team.<br><br>I found a problem between PVE and
LVM.<br><br>Considering that if it is used LVM as block device for the
virtual disks of<br>the VMs, Linux give us a great comfort, but the
problem is that if I in<br>"online mode" enlarge a Physical Volume and
after enlarge a Logical Volume<br>by CLI, in PVE, the VM can not see the
new free hard disk space without<br>partition.<br><br>In previous
versions of PVE, this task was possible do it with much
easily.<br><br>Moreover, i think that this feature is very util, due to
that in the actual<br>condition, it force me to power off the VM and
start it again, so that being<br>a server (talking about of the VM) that
is in a production environment, only<br>can I do it outside of working
hours.<br><br>So i would like to ask if the PVE team have interest in
correcting this<br>problem.<br><br>Best
regards<br>Cesar<br><br>______________________________
_________________<br>pve-devel mailing list<br><a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a><br><a href="http://pve.proxmox.com/cgi-" target="_blank">http://pve.proxmox.com/cgi-</a>
bin/mailman/listinfo/pve-devel<br>______________________________
_________________<br>pve-devel mailing list<br><a href="mailto:pve-devel@pve.proxmox.com" target="_blank">pve-devel@pve.proxmox.com</a><br><a href="http://pve.proxmox.com/cgi-" target="_blank">http://pve.proxmox.com/cgi-</a>
bin/mailman/listinfo/pve-devel<br></blockquote></div></blockquote></div></blockquote></div></blockquote></div></blockquote></div>