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
On Fri, Feb 12, 2010 at 10:55 AM, 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
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
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 othe
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 b
On Fri, Feb 12, 2010 at 1:08 PM, Daniel Carosone 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 t
