[Lxc-users] lxc-create -B zfs

[Serge Hallyn]

Quoting Tamas Papp (tompos at martos.bme.hu):
> On 06/18/2013 04:14 AM, Serge Hallyn wrote:
> 
> hi Serge,
> 
> > Quoting Tamas Papp (tompos at martos.bme.hu):
> >> On 06/10/2013 03:41 PM, Serge Hallyn wrote:
> >>> Quoting Tamas Papp (tompos at martos.bme.hu):
> >>>> hi,
> >>>>
> >>>> # lxc-create -n pony -t ubuntu -B zfs --zfsroot=tank/lxc
> >>> Hm.  Mine is simply called 'lxc', and that works.  So it sounds like I'm
> >>> doing something wrong in parsing the zfsroot, but I can't offhand see
> >>> in the code where.
> >>>
> >>> Could you run this through 'strace -f -odebutfile' and look in debugfile
> >>> for the exec of 'zfs create'?
> >> hi,
> >>
> >> Sorry, I could get back to this just now:
> >>
> >> log.103022:execve("/sbin/zfs", ["zfs", "create",
> >> "-omountpoint=/var/lib/lxc/test123/rootfs", "tank/lxc/test123"], [/*
> >> 21 vars */]) = 0
> >>
> >> From cli it works fine.
> >>
> >> I can send the whole log file, if you want.
> > Yes, please do - to me personally depending on the size, to spare the
> > list.
> 
> Shame on me, I absolutely forgot to answer this email.
> 
> This one works fine:
> 
> # lxc-create -n eee -t ubuntu -B zfs --zfsroot tank/lxc

Can zfs pools be any directory hierarchy depth?  Examples I had seen
were always just one (i.e. 'tank'), so I always just used 'lxc'.
If they can be any depth, the modifications to src/lxc/bdev.c to make
that work shouldn't be very intricate.

-serge