On Fri, 17 Apr 2009, Mark J Musante wrote:
The dependency is based on the names.
I should clarify what I mean by that. There are actually two dependencies
here: one is based on dataset names, and one is based on snapshots and
clones.
If there are two datasets, pool/foo and pool/foo/bar, t
The dependency is based on the names. Try renaming
testpool/testfs2/clone1 out of the hierarchy:
zfs rename testpool/testfs2/clone1 testpool/foo
Then it should be possible to destroy testpool/testfs2.
On Fri, 17 Apr 2009, Grant Lowe wrote:
I was wondering if there is a solution for this
I was wondering if there is a solution for this. I've been able to replicate a
similar problem on a different server. Basically I'm still unable to use zfs
destroy on a filesystem, that was a parent filesystem and is now a child
filesystem after a promotion.
bash-3.00# zpool history
History f
I'm having a very difficult time destroying a zone. Here's the skinny:
bash-3.00# zfs get origin | grep d01
r12_data/d01 origin
r12_data/d01/.clone.12052...@12042008 -
r12_data/d01-receive origin-
-
r12_dat
