Hello zfs-discuss, snv_29/sparc We created local zone with no sparse filesystems (whole root) - so /sbin /lib is copied into zone and not shared with local zone. We did it ''coz it''s required by current JES. Then we wanted to add given dataset into that zone - it wasn''t mounted and local zone administrator couldn''t list zfs filesystems, etc. The problem is that ZFS is deliverd in two packages: SUNWzfsu, SUNWzfsr. Now SUNWzfsu has SUNW_PKG_ALLZONES=true and SUNW_PKG_HOLLOW=false. Which is ok. However SUNWzfsr has SUNW_PKG_ALLZONES=true and SUNW_PKG_HOLLOW=true - which will result in not copying /sbin/zfs /sbin/zpool and libraries - all of them are required in order to zfs work in local zone (it will work with standard zones as /lib and /sbin are shared with global zone). Probably /sbin/zfs /sbin/zpool /lib/libzfs* /lib/sparv9/libzfs* (and other architectures) should be deliverd as part of SUNWzfsu. I did copied into local zone this files manually and it seems like ZFS is now working in a zone. -- Best regards, Robert mailto:rmilkowski at task.gda.pl
On Wed, Dec 21, 2005 at 12:15:31PM +0100, Robert Milkowski wrote:> Hello zfs-discuss, > > snv_29/sparc > > We created local zone with no sparse filesystems (whole root) - so > /sbin /lib is copied into zone and not shared with local zone. > We did it ''coz it''s required by current JES. > > Then we wanted to add given dataset into that zone - it wasn''t > mounted and local zone administrator couldn''t list zfs filesystems, > etc. > > The problem is that ZFS is deliverd in two packages: SUNWzfsu, > SUNWzfsr. Now SUNWzfsu has SUNW_PKG_ALLZONES=true and > SUNW_PKG_HOLLOW=false. Which is ok. > However SUNWzfsr has SUNW_PKG_ALLZONES=true and SUNW_PKG_HOLLOW=true > - which will result in not copying /sbin/zfs /sbin/zpool and > libraries - all of them are required in order to zfs work in local > zone (it will work with standard zones as /lib and /sbin are shared > with global zone). > > Probably /sbin/zfs /sbin/zpool /lib/libzfs* /lib/sparv9/libzfs* (and > other architectures) should be deliverd as part of SUNWzfsu.We can''t do that; you can''t deliver stuff into / in a /usr package. It sounds like the kernel bits of SUNWzfsr need to move into a separate package (SUNWzfskr?). - jonathan -- Jonathan Adams, Solaris Kernel Development
FYI, I''ve filed: 6366258 SUNWzfsr breaks in whole root zones To track this issue. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
Hello Jonathan, Wednesday, December 21, 2005, 11:22:31 PM, you wrote: JA> On Wed, Dec 21, 2005 at 12:15:31PM +0100, Robert Milkowski wrote:>> Hello zfs-discuss, >> >> snv_29/sparc >> >> We created local zone with no sparse filesystems (whole root) - so >> /sbin /lib is copied into zone and not shared with local zone. >> We did it ''coz it''s required by current JES. >> >> Then we wanted to add given dataset into that zone - it wasn''t >> mounted and local zone administrator couldn''t list zfs filesystems, >> etc. >> >> The problem is that ZFS is deliverd in two packages: SUNWzfsu, >> SUNWzfsr. Now SUNWzfsu has SUNW_PKG_ALLZONES=true and >> SUNW_PKG_HOLLOW=false. Which is ok. >> However SUNWzfsr has SUNW_PKG_ALLZONES=true and SUNW_PKG_HOLLOW=true >> - which will result in not copying /sbin/zfs /sbin/zpool and >> libraries - all of them are required in order to zfs work in local >> zone (it will work with standard zones as /lib and /sbin are shared >> with global zone). >> >> Probably /sbin/zfs /sbin/zpool /lib/libzfs* /lib/sparv9/libzfs* (and >> other architectures) should be deliverd as part of SUNWzfsu.JA> We can''t do that; you can''t deliver stuff into / in a /usr package. It JA> sounds like the kernel bits of SUNWzfsr need to move into a separate package JA> (SUNWzfskr?). ok, makes sense. -- Best regards, Robert mailto:rmilkowski at task.gda.pl