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 _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
