Quoting Serge Hallyn ([email protected]): > Quoting zoolook ([email protected]): > > Hi Serge, > > > > > > On Tue, Jun 18, 2013 at 5:57 PM, zoolook <[email protected]> wrote: > > > On Tue, Jun 18, 2013 at 5:39 PM, Serge Hallyn <[email protected]> > > > wrote: > > >> Exactly what code (git commit id or distro+pkg) are you using? > > > > > > > > > Installed: 0.9.0.0~staging~20130612-1544-0ubuntu1~ppa1~raring1 > > > > > > on saucy, with ppa:ubuntu-lxc/daily > > (0.9.0.0~staging~20130612-1544-0ubuntu1~ppa1~saucy1), no patches > > applied. > > > > sysadmin@lxc3:~$ sudo lvs > > LV VG Attr LSize Pool Origin Data% Move > > Log Copy% Convert > > lxc-test1-root vg_vmstorage -wi-a---- 7,81g > > > > sysadmin@lxc3:~$ sudo lxc-clone -s -p /srv/lxc -P /srv/lxc -o test1 -n > > test101 > > Volume group "vg_vmstorage" has insufficient free space (617 > > extents): 2097 required. > > lxc: could not create /dev/vg_vmstorage/lxc-test101-root snapshot of > > all right, not sure why yet, but the naming of your rootfs is somehow > causing the problem. I was able to reproduce this when I renamed my > test101 rootfs to xxx-test101-xxx. > > I'll look into why later today. Thanks!
Oh I see the problem. The update_name_and_paths() only replaces the container name if it is a whole word. Need to think about whether it is safe to change that. (What if the container name is 'c'?) ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Lxc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxc-users
