Re: [zfs-discuss] Removing Cloned Snapshot
On Fri, 12 Feb 2010, Daniel Carosone wrote: You can use zfs promote to change around which dataset owns the base snapshot, and which is the dependant clone with a parent, so you can deletehe other - but if you want both datasets you will need to keep the snapshot they share. Right. The other option is to zfs send the snapshot to create a copy instead of a clone. Once the zfs recv completes, the snapshot can be destroyed. Of course, it takes much longer to do this, as zfs is going to create a full copy of the snapshot. The appeal of clones is that they, at least initially, take no extra space, and also that they're nearly instantaneous. But they require the snapshot to remain for the lifetime of the clone. Regards, markm ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Removing Cloned Snapshot
On Fri, Feb 12, 2010 at 09:50:32AM -0500, Mark J Musante wrote: The other option is to zfs send the snapshot to create a copy instead of a clone. One day, in the future, I hope there might be a third option, somewhat as an optimimsation. With dedup and bp-rewrite, a new operation could be created that takes the shared data and makes it uniquely-referenced but deduplicated data. This could be a lot more efficient and less disruptive because of the advanced knnowledge that the data must already be the same. Whether its worth the implementation effort is another issue, but in the meantime we have plenty of time to try and come up with a sensible name for it. unclone is too boring :) -- Dan. pgpZRhozoZ5Cf.pgp Description: PGP signature ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Removing Cloned Snapshot
On Fri, Feb 12, 2010 at 1:08 PM, Daniel Carosone d...@geek.com.au wrote: With dedup and bp-rewrite, a new operation could be created that takes the shared data and makes it uniquely-referenced but deduplicated data. This could be a lot more efficient and less disruptive because of the advanced knnowledge that the data must already be the same. That's essentially what a send/recv does when dedup is enabled. -B -- Brandon High : bh...@freaks.com There is absolutely no substitute for a genuine lack of preparation. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] Removing Cloned Snapshot
I am getting the following message when I try and remove a snapshot from a clone: bash-3.00# zfs destroy data/webser...@sys_unconfigd cannot destroy 'data/webser...@sys_unconfigd': snapshot has dependent clones use '-R' to destroy the following datasets: The datasets are being used, so why can't I delete the snapshot? Thanks ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Removing Cloned Snapshot
On Fri, Feb 12, 2010 at 10:55 AM, Tony MacDoodle tpsdoo...@gmail.com wrote: I am getting the following message when I try and remove a snapshot from a clone: bash-3.00# zfs destroy data/webser...@sys_unconfigd cannot destroy 'data/webser...@sys_unconfigd': snapshot has dependent clones use '-R' to destroy the following datasets: Is there something else below that line? Like the name of the clones? The datasets are being used, so why can't I delete the snapshot? because it's used as base for clones. -- Fajar ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Removing Cloned Snapshot
On Thu, Feb 11, 2010 at 10:55:20PM -0500, Tony MacDoodle wrote: I am getting the following message when I try and remove a snapshot from a clone: bash-3.00# zfs destroy data/webser...@sys_unconfigd cannot destroy 'data/webser...@sys_unconfigd': snapshot has dependent clones use '-R' to destroy the following datasets: The datasets are being used, so why can't I delete the snapshot? Clones are writable copies of snapshots, and share space with the snapshot that is their basis (initially, all the space). That space belongs to the snapshot, which in turn belongs to another dataset (from which it was originally taken). For clones, you will see that referenced is often much more than usedbydataset, as a result. You can use zfs promote to change around which dataset owns the base snapshot, and which is the dependant clone with a parent, so you can deletehe other - but if you want both datasets you will need to keep the snapshot they share. -- Dan. pgpjCc6bUAkTe.pgp Description: PGP signature ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
