Quick question. I had a dataset that could not be deleted because it was marked as busy. Well turns out it was because i had filebrowser app still running. In the process of deleting dataset i used the cli. I saw on some older forums that users unmounted the pool to try and delete dataset. So i unmounted my pool where the dataset was and tried to delete it. It still didnt work until i stopped the filebrowser app. My question, can me manually unmounting pool in cli hurt anything? and will truenas automatically remount the pool on the next boot? Should i restore from a snapshot before this process or will it be okay?
If you unmount the pool, I believe you will need to re-mount it yourself. Do this via the GUI otherwise odd things may occur
I didnt unmount pool. I only unmounted dataset so i did zfs unmount pool/data.
I never ran zpool unmount.
From what i have found in research zfs unmount only unmounts the specific dataset which removes mountpoint while zpool unmount unmounts the entire pool removing all mountpoints.
Since all of this i have rebooted truenas and it did automatically remount everything and everything seems to be working fine. I just wanted to make sure that it wouldn’t affect performance or cause instability. Just making sure i didn’t screw anything up.
It might throw off the middleware or GUI, but I don’t see why your data (in other datasets) would be at risk.
The more important thing is to be able to safely delete a dataset, without using a forceful unmount.
What file browser app?
In the apps section if you go to discover apps and install filebrowser. it allows you to look at files in your dataset pretty cool. Anyways filebrowser pointed to my root pool so because the app was running the dataset was busy.
Also even when i unmounted the dataset i still couldnt remove it until i stopped the app.