[PVE-User] Pve 4.0
Wolfgang Bumiller
w.bumiller at proxmox.com
Mon Jul 6 06:17:16 CEST 2015
I'm not sure what difference that would make for the container though.
With qemu it would be understandable, but with containers I don't immediately
see where that would go wrong.
It works fine on a single system anyway.
/dev/loop0 3.9G 8.0M 3.6G 1% /mnt/tmp
changed to
/dev/loop0 4.8G 8.0M 4.6G 1% /mnt/tmp
> On July 3, 2015 at 4:38 PM Alexandre DERUMIER <aderumier at odiso.com> wrote:
>
>
> >>-c, --set-capacity loopdev
>
> qemu-img resize volume.raw +1G : ok
> losetup -c /dev/loopx : ok
>
> but now, resize2fs is not working inside the container.
> (so it need to be mounted on the host, so not possible with container online)
>
> I'll try to find some infos about this.
>
> ----- Mail original -----
> De: "Wolfgang Bumiller" <w.bumiller at proxmox.com>
> À: "aderumier" <aderumier at odiso.com>
> Cc: "dietmar" <dietmar at proxmox.com>, "proxmoxve" <pve-user at pve.proxmox.com>
> Envoyé: Vendredi 3 Juillet 2015 14:20:20
> Objet: Re: [PVE-User] Pve 4.0
>
> > I'm not sure we can do it "online" with loop device on top of raw file.
> Maybe.
>
> From losetup(1):
> -c, --set-capacity loopdev
> Force the loop driver to reread the size of the file associated with the
> specified loop device.
>
> Worth a try?
>
> On Fri, Jul 03, 2015 at 11:27:04AM +0200, Alexandre DERUMIER wrote:
> > >> - I saw it not possible to resize disk of an lxc container after
> > >> creation, is it a restriction ?
> > >
> > >We try to implement that later.
> >
> > I'm not sure we can do it "online" with loop device on top of raw file.
> > Offline should be possible.
> >
> > For block device (zfs, rbd,..) I think we can resize online. (and snapshot
> > too)
> >
> >
> > ----- Mail original -----
> > De: "dietmar" <dietmar at proxmox.com>
> > À: "proxmoxve" <pve-user at pve.proxmox.com>, "Jérémy Carnus"
> > <jeremy at jcarnus.fr>
> > Envoyé: Mercredi 1 Juillet 2015 21:17:33
> > Objet: Re: [PVE-User] Pve 4.0
> >
> > > - I saw it not possible to resize disk of an lxc container after
> > > creation, is it a restriction ?
> >
> > We try to implement that later.
> >
> > > - Trying to migrate a vz container to a lxc container using backup /
> > > restore leads me to a "TASK ERROR: Insecure dependency in unlink while
> > > running with -T switch at /usr/share/perl5/PVE/Tools.pm line 187." when
> > > restoring the zip archive in the pve4.0
> >
> > Migration is currently not implemented, but we plan to implement (offline)
> > migration soon.
> >
> > _______________________________________________
> > pve-user mailing list
> > pve-user at pve.proxmox.com
> > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >
> > _______________________________________________
> > pve-user mailing list
> > pve-user at pve.proxmox.com
> > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
More information about the pve-user
mailing list