On Thu, Feb 21, 2013 at 8:34 AM, Jan Owoc <jso...@gmail.com> wrote: > Hi Markus, > > On Thu, Feb 21, 2013 at 6:44 AM, Markus Grundmann <mar...@freebsduser.eu> > wrote: > > I think the "zfs allow|deny" feature is only for filesystems. I wish me a > > feature to protect the complete pool. The property is restricted to zpool > > commands. > > > > On my notebook I have created a pool with simulated drives > (gpt/drive1..n) > > and without any warnings or "you are sure (y/n)" I can destroy them after > > one second. > > > [SNIP] > > > > For my personal reasons I will try to rewrite some pieces of the current > > source code in FreeBSD to get the wanted functionality for me. > > Please wish me good luck *g* > > I think Mike's solution is exactly what you are looking for. You can > make a snapshot, hold it, and then zfs destroy (and even zfs destroy > -r) will fail. The only thing you can do is run the command(s) to > "un-hold" the snapshot. > > On Wed, Feb 20, 2013 at 4:08 PM, Mike Gerdts <mger...@gmail.com> wrote: > > # zfs create a/1 > > # zfs create a/1/hold > > # zfs snapshot a/1/hold@hold > > # zfs hold 'saveme!' a/1/hold@hold > > # zfs holds a/1/hold@hold > > NAME TAG TIMESTAMP > > a/1/hold@hold saveme! Wed Feb 20 15:06:29 2013 > > # zfs destroy -r a/1 > > cannot destroy 'a/1/hold@hold': snapshot is busy > > Does this do what you want? (zpool destroy is already undo-able) > > Jan > > That suggestion makes the very bold assumption that you want a long-standing snapshot of the dataset. If it's a rapidly changing dataset, the snapshot will become an issue very quickly.
_______________________________________________ zfs-discuss mailing list firstname.lastname@example.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss