freebsd stable - Jul 2017 - cannot destroy faulty zvol

Hi,


I cannot destroy a zvol for a reason that I don't understand:


[root at san1:~]# zfs list -t all | grep worker182
zfsroot/userdata/worker182-bad        1,38G  1,52T   708M  -
[root at san1:~]# zfs destroy -R zfsroot/userdata/worker182-bad
cannot destroy 'zfsroot/userdata/worker182-bad': dataset already exists
[root at san1:~]#


also noitice that this zvol is faulty:


   pool: zfsroot
  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: http://illumos.org/msg/ZFS-8000-8A
   scan: scrub in progress since Sat Jul 22 15:01:37 2017
         18,7G scanned out of 130G at 75,0M/s, 0h25m to go
         0 repaired, 14,43% done
config:

         NAME            STATE     READ WRITE CKSUM
         zfsroot         ONLINE       0     0     4
           mirror-0      ONLINE       0     0     8
             gpt/zroot0  ONLINE       0     0     8
             gpt/zroot1  ONLINE       0     0     8

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

         zfsroot/userdata/worker182-bad:<0x1>
         <0xc7>:<0x1>


is this weird error "cannot destroy: already exists" related to the
fact
that the zvol is faulty ? Does it indicate that metadata is probably 
faulty too ? Anyway, is there a way to destroy this dataset ?


Thanks.

Hi,

On 22.07.2017 17:08, Eugene M. Zheganin wrote:
>
> is this weird error "cannot destroy: already exists" related to
the
> fact that the zvol is faulty ? Does it indicate that metadata is 
> probably faulty too ? Anyway, is there a way to destroy this dataset ?
Follow-up: I sent a similar zvol of the thexactly same size into the 
faulty one, zpool errors are gone, still cannot destroy the zvol. Is 
this a zfs bug ?

Eugene.