Ghost zfs entries from failed VM creations

[BenCranston]

Greetings!
I'm running TrueNAS 12.0 on a Dell R710. I was trying to create VMs, but discovered that my CPU didn't meet the requirement. I upgraded to a pair of x5675 and am good to go now. However my attempts left 'cruft' sticking around in the system. issuing a:
zfs list
I get a bunch of what I'd expect and then a few like this:
Pool/iocage/jails/CoreOS_Docker-9749ml 60.1G 26.6T 179K -
That jail does not exist. It's not present at /mnt/Pool/iocage/jails via the shell. I does however show up in the GUI via the storage view of my pools. there are a couple that do not show up in the GUI. Same situation, nothing on the volume. How do I get rid of them? I'm a bit frightened to just plain delete the zvol via the GUI. And if that's the right path, how to I get rid of the ones that don't show up in the GUI? Thanks.

 

[sretalla]

zfs destroy Pool/iocage/jails/CoreOS_Docker-9749ml

 

[BenCranston]

Thank you. I'm assuming that's safe and won't effect anything else. I'm equating this to a zfs "database" edit, right?

 

[sretalla]

I'm equating this to a zfs "database" edit, right?

I don't know you could say that it's exactly just an edit to the DB, but it will not have any impact on any other datasets in your pool, which is what I think you're worried about.

If there were child datasets of that one, the destroy would fail (and tell you that you need to use -r or --recursive to get it to eliminate the children also), but I guess you actually want that in this case as those jails are gone as far as you're concerned anyway.

 

[BenCranston]

Thank you. that did the trick and the ghosts are gone.