> From: Cindy Swearingen [mailto:cindy.swearin...@oracle.com]
>
> A temporary clone is created for an incremental receive and
> in some cases, is not removed automatically.
>
> 1. Determine clone names:
> # zdb -d | grep %
>
> 2. Destroy identified clones:
> # zfs destroy
>
> 3. Destroy snaps
Hi Ned,
If you do incremental receives, this might be CR 6860996:
%temporary clones are not automatically destroyed on error
A temporary clone is created for an incremental receive and
in some cases, is not removed automatically.
Victor might be able to describe this better, but consider
the f
Is the pool mounted? I ran into this problem frequently, until I set mountpoint
to legacy. It may be that I had to destroy the filesystem afterwards, but since
I stopped mounting the backup target everything runs smoothly. Nevertheless I
agree it would be nice to find the root cause for this.
--
A
This is the problem:
[r...@nasbackup backup-scripts]# zfs destroy
storagepool/nas-lyricp...@nasbackup-2010-05-14-15-56-30
cannot destroy 'storagepool/nas-lyricp...@nasbackup-2010-05-14-15-56-30':
dataset already exists
This is apparently a common problem. It's happened to me twice already, a
