Just did my first dataset delegation, so be gentle :) Was initially terrified to see that changes to the mountpoint in the non-global zone were visible in the global zone. Then I realised it wasn''t actually mounted (except in the delegated zone). But I couldn''t see any obvious indication that the dataset was delegated to another zone in zfs list. Eventually I found the ''zoned'' property. Couple of thoughts: 1) would it be worth changing ''zfs list'' to clarify where a dataset is actually mounted? 2) Is there any way to indicate _what_ zone a dataset is mounted in (other than greppping the zones configuration)? -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/
zfs mount should show where all your datasets are mounted. I too was confused with the zfs list readout. On Wed, 2006-09-06 at 07:37, Dick Davies wrote:> Just did my first dataset delegation, so be gentle :) > > Was initially terrified to see that changes to the mountpoint in the non-global > zone were visible in the global zone. > > Then I realised it wasn''t actually mounted (except in the delegated zone). > But I couldn''t see any obvious indication that the dataset was delegated to > another zone in zfs list. > Eventually I found the ''zoned'' property. Couple of thoughts: > > 1) would it be worth changing ''zfs list'' to clarify where a dataset > is actually mounted? > 2) Is there any way to indicate _what_ zone a dataset is mounted in > (other than greppping the zones configuration)? > > -- > Rasputin :: Jack of All Trades - Master of Nuns > http://number9.hellooperator.net/ > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
That''s a bit nicer, thanks. Still not that clear which zone they belong to though - would it be an idea to add a ''zone'' property be a string == zonename ? On 06/09/06, Kenneth Mikelinich <ken.mikelinich at unh.edu> wrote:> zfs mount > > should show where all your datasets are mounted. > > I too was confused with the zfs list readout. > > > > On Wed, 2006-09-06 at 07:37, Dick Davies wrote: > > Just did my first dataset delegation, so be gentle :) > > > > Was initially terrified to see that changes to the mountpoint in the non-global > > zone were visible in the global zone. > > > > Then I realised it wasn''t actually mounted (except in the delegated zone). > > But I couldn''t see any obvious indication that the dataset was delegated to > > another zone in zfs list. > > Eventually I found the ''zoned'' property. Couple of thoughts: > > > > 1) would it be worth changing ''zfs list'' to clarify where a dataset > > is actually mounted? > > 2) Is there any way to indicate _what_ zone a dataset is mounted in > > (other than greppping the zones configuration)? > > > > -- > > Rasputin :: Jack of All Trades - Master of Nuns > > http://number9.hellooperator.net/ > > _______________________________________________ > > zfs-discuss mailing list > > zfs-discuss at opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/
On Wed, Sep 06, 2006 at 03:53:52PM +0100, Dick Davies wrote:> That''s a bit nicer, thanks. > Still not that clear which zone they belong to though - would > it be an idea to add a ''zone'' property be a string == zonename ?Yes, this is possible, but it''s annoying because the actual owning zone isn''t stored with the dataset (nor should it be). We''d have to grovel around every zone''s configuration file, which is certainly doable, just annoying. In addition, it''s possible (though not recommended) to have a single dataset in multiple zones. The only real use case would be a read-only, unmounted dataset whose snapshots could serve as a clone source for other delegated datasets. Since this is extremely rare, it would probably suffice to have a special string like "(shared)" to indicate that it is being shared between multiple zones. Feel free to file an RFE. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
On Wed, Sep 06, 2006 at 08:34:26AM -0700, Eric Schrock wrote:> > Feel free to file an RFE. >Oops, found one already: 6313352 ''zpool list'' & ''zfs list'' should add ''-z'' & ''-Z'' to identifier a zone - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
On 06/09/06, Eric Schrock <eric.schrock at sun.com> wrote:> On Wed, Sep 06, 2006 at 03:53:52PM +0100, Dick Davies wrote: > > That''s a bit nicer, thanks. > > Still not that clear which zone they belong to though - would > > it be an idea to add a ''zone'' property be a string == zonename ? > > Yes, this is possible, but it''s annoying because the actual owning zone > isn''t stored with the dataset (nor should it be). We''d have to grovel > around every zone''s configuration file, which is certainly doable, just > annoying.Oh God no. That''s exactly what I wanted to avoid. Why wouldn''t you want it stored in the dataset, out of interest?> In addition, it''s possible (though not recommended) to have a > single dataset in multiple zones.Ah Ok, that explains why a single string wouldn''t cut it (although it sounds insane to me)!> The only real use case would be a > read-only, unmounted dataset whose snapshots could serve as a clone > source for other delegated datasets.I''m reading that as ''the only real use case for 1 dataset in multiple zones'' (sorry if I''m misunderstanding you)? -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/
On Wed, Sep 06, 2006 at 04:52:48PM +0100, Dick Davies wrote:> > Oh God no. That''s exactly what I wanted to avoid. > Why wouldn''t you want it stored in the dataset, out of interest?There are a couple of reasons: - We don''t want to re-create the same information in multiple places. Keeping both the zone configuration file and the on-disk state in sync would be difficult. - The association of a dataset to a zone is a property of the zone, not the dataset. This is particularly important if you want to migrate zones with delegated datasets between machines, or export and import your pool on a machine with a different zone configuration. - Unlike NFS options or mountpoints, the dataset is part of a larger zone configuration, and cannot replace the zone configuration file entirely. Ideally, we would have liked to not have the ''zoned'' property at all, but it was necessary to enforce sane behavior between the global and local zone.> > I''m reading that as ''the only real use case for 1 dataset in multiple zones'' > (sorry if I''m misunderstanding you)? >Yep. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
As user properties are coming then maybe when a fs is mounted in a local zone a user property would be set, like zone_mounted=test1. Perhaps during each mount such property would be created. In case with several zones just put names after , or something similar. ?? This message posted from opensolaris.org