zfs discuss - Jan 2010 - unable to zfs destroy

this one has me alittle confused. ideas?

jack at opensolaris:~# zpool import z
cannot mount ''z/nukeme'': mountpoint or dataset is busy
cannot share ''z/cle2003-1'': smb add share failed
jack at opensolaris:~# zfs destroy z/nukeme
internal error: Bad exchange descriptor
Abort (core dumped)
jack at opensolaris:~# adb core
core file = core -- program ``/sbin/zfs'''' on platform i86pc
SIGABRT: Abort
$c
libc_hwcap1.so.1`_lwp_kill+0x15(1, 6, 80462a8, fee9bb5e)
libc_hwcap1.so.1`raise+0x22(6, 0, 80462f8, fee7255a)
libc_hwcap1.so.1`abort+0xf2(8046328, fedd0000, 8046328, 8086570, 8086970, 400)
libzfs.so.1`zfs_verror+0xd5(8086548, 813, fedc5178, 804635c)
libzfs.so.1`zfs_standard_error_fmt+0x225(8086548, 32, fedc5178, 808acd0)
libzfs.so.1`zfs_destroy+0x10e(808acc8, 0, 0, 80479c8)
destroy_callback+0x69(808acc8, 8047910, 80555ec, 8047910)
zfs_do_destroy+0x31f(2, 80479c8, 80479c4, 80718dc)
main+0x26a(3, 80479c4, 80479d4, 8053fdf)
_start+0x7d(3, 8047ae4, 8047ae8, 8047af0, 0, 8047af9)
^d
jack at opensolaris:~# uname -a
SunOS opensolaris 5.11 snv_130 i86pc i386 i86pc
jack at opensolaris:~# zpool status -v z
  pool: z
 state: ONLINE
status: One or more devices has experienced an error resulting in data
	corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
	entire pool from backup.
   see: sun.com/msg/ZFS-8000-8A
 scrub: scrub in progress for 0h39m, 19.15% done, 2h46m to go
config:

	NAME        STATE     READ WRITE CKSUM
	z           ONLINE       0     0     2
	  c3t0d0s7  ONLINE       0     0     4
	  c3t1d0s7  ONLINE       0     0     0
	  c2d0      ONLINE       0     0     4

errors: Permanent errors have been detected in the following files:

        z/nukeme:<0x0>

jack at opensolaris:~# zfs list z/nukeme
NAME       USED  AVAIL  REFER  MOUNTPOINT
z/nukeme  49.0G   496G  49.0G  /z/nukeme
jack at opensolaris:~# zdb -d z/nukeme 0x0
zdb: can''t open ''z/nukeme'': Device busy

there is also no mount point /z/nukeme

any ideas how to nuke /z/nukeme    ?

On Fri, 8 Jan 2010, Rob Logan wrote:
>
> this one has me alittle confused. ideas?
>
> jack at opensolaris:~# zpool import z
> cannot mount ''z/nukeme'': mountpoint or dataset is busy
> cannot share ''z/cle2003-1'': smb add share failed
> jack at opensolaris:~# zfs destroy z/nukeme
> internal error: Bad exchange descriptor
EBADE is used by ZFS to indicate checksum errors, which supports the zpool 
status output:
> config:
>
> 	NAME        STATE     READ WRITE CKSUM
> 	z           ONLINE       0     0     2
> 	  c3t0d0s7  ONLINE       0     0     4
> 	  c3t1d0s7  ONLINE       0     0     0
> 	  c2d0      ONLINE       0     0     4
>
> errors: Permanent errors have been detected in the following files:
>
>        z/nukeme:<0x0>
So, yeah, without a way for zfs to repair itself, it looks like the only 
way forward is to destroy the zpool and restore from a backup.


Regards,
markm