> > The initial idea was to make a dataset/snapshot and > clone (fast) and then separate the clone from its > snapshot. The clone could be then used as a new > independant dataset. > > > > The send/receive subcommands are probably the only > way to duplicate a dataset. > > I'm still not sure I understand what about clones makes you not want to > use them. What do you mean by "separate the clone from its snapshot"? > Is it that you want to destroy the filesystem that > the clone was created from? To do that you can use 'zfs promote'. Is it > that you want to guarantee space availability to overwrite it? To do > that you can use 'zfs set reservation'. > > --matt
I didn't ask the original question, but I have a scenario where I want to use clone as well and encounter a (designed?) behaviour I am trying to understand. I create a filesystem A with ZFS and modify it to a point where I create a snapshot [EMAIL PROTECTED] Then I clone that snapshot to create a new filesystem B. I seem to have two filesystem "entities" I can make independant modifications and snapshots with/on/from. The problem I am running into is that when modifying A and wanting to rollback to the snapshot [EMAIL PROTECTED] I can't do that as long as the clone B is mounted. Is this a case where I would benefit from the ability to sperate the clone? Or is this something not possible with ZFS? Thanks for any answers This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
