I messed up my pool by doing zfs send...recive So I got the following :
zpool list
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
rpool 928G 17.3G 911G 1% 1.00x ONLINE -
tank1 928G 35.8G 892G 3% 1.00x ONLINE -
So I have "tank1" pool.
zfs get all tank1
NAME PROPERTY VALUE SOURCE
tank1 type volume -
Haa...I also have "tank1" as a volume....
So I wanted to delete the volume :
zfs destroy tank1
cannot destroy 'tank1': dataset already exists
So let me delete the pool...Please...
zpool destroy tank1
cannot open 'tank1': operation not applicable to datasets of this type
Another try : (just want to rename...)
zfs rename tank1 tank1/kuku
cannot create 'tank1/kuku': parent is not a filesystem
So how can I resolve this issue ?
Try
zpool export tank1
zpool import tank1 new_name
This is what I am getting :
zpool export tank1
zpool import tank1 kuku
Assertion failed: !ZFS_IS_VOLUME(zhp), file ../common/libzfs_mount.c, line 446, function zfs_share
Abort (core dumped)
Try create new zpool using disks from "tank1" with:
zpool create -f new_pool disks
Thanks, but I am still getting :
zpool create -f tank1 mirror c1t50000F000B114807d0 c1t50000F000B114817d0
invalid vdev specification
the following errors must be manually repaired:
/dev/dsk/c1t50000F000B114807d0s0 is part of active ZFS pool kuku. Please see zpool(1M).
OK, so try zpool export kuku
first, then zpool create
.
Sorry I didn'nt understand your last message.
I tried again :
root@storage01:~# zfs destroy kuku
cannot destroy 'kuku': dataset already exists
root@storage01:~# zpool destroy kuku
cannot open 'kuku': operation not applicable to datasets of this type
So inspite the fact that the name was changed the OS still one time thinks that the object is a volume and one time is a pool.
Well, try exporting that changed zpool as I indicated above, then try creating new zpool with the "-f" flag.
Great you solved the issue.
Thanks a lot.