On Thu, Apr 23, 2009 at 09:59:33AM -0600, Matthew Ahrens wrote: > "zfs destroy [-r] -p" sounds great. > > I'm not a big fan of the "-t template". Do you have conflicting snapshot > names due to the way your (zones) software works, or are you concerned > about sysadmins creating these conflicting snapshots? If it's the former, > would it be possible to change the zones software to avoid it?
I think the -t option -- automatic snapshot name conflict resolution -- makes a lot of sense in the context of snapshots and clones mostly managed by a system component (zonedm, beadm) but where users can also create snapshots (e.g., for time slider, backups): you don't want the users to create snapshot names that will later prevent zoneadm/beadm destroy. Making the users responsible for resolving such conflicts seems not user-friendly to me. However, if we could just avoid the conflicts in the first place then we'd not need an option for automatic snapshot name conflict resolution. Conflicts could be avoided by requiring that all snapshot names of a dataset and of clones of snapshots of that dataset, and so on, be unique. Snapshot name uniqueness could be a property of the root dataset of a snapshot/clone tree. Nico -- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
