I have a share with no files in it. When I try removing it I get this in the logs:

Jan  5 13:52:38 Hades shfs: /usr/sbin/zfs unmount 'disk11/Other'
Jan  5 13:52:38 Hades shfs: /usr/sbin/zfs destroy 'disk11/Other'
Jan  5 13:52:38 Hades root: cannot destroy 'disk11/Other': dataset is busy
Jan  5 13:52:38 Hades shfs: retval: 1 attempting 'destroy'
Jan  5 13:52:38 Hades shfs: /usr/sbin/zfs mount 'disk11/Other'
Jan  5 13:52:38 Hades shfs: /usr/sbin/zfs unmount 'disk12/Other'
Jan  5 13:52:38 Hades shfs: /usr/sbin/zfs destroy 'disk12/Other'
Jan  5 13:52:38 Hades root: cannot destroy 'disk12/Other': dataset is busy
Jan  5 13:52:38 Hades shfs: retval: 1 attempting 'destroy'
Jan  5 13:52:38 Hades shfs: /usr/sbin/zfs mount 'disk12/Other'
Jan  5 13:52:38 Hades emhttpd: shcmd (3111317): rm '/boot/config/shares/Other.cfg'

 

The 2 drives it is complaining about are ZFS formatted. If I manually delete the folder via file explorer or windows file explorer they delete fine and then immediately re-appear.

 

I tried using rm -r as well and it just gives back:

 

rm: cannot remove '/mnt/disk11/Other': Device or resource busy

 

any thoughts? Its not harming anything but its bugging me haha

They are not folders but zfs datasets, and there should be something using them preventing them from being destroyed.

4 minutes ago, JorgeB said:

They are not folders but zfs datasets, and there should be something using them preventing them from being destroyed.

is there a way for me to find out? The folder is empty, so if I lose whatever hidden stuff is in it I don't care about it. I did have the bfs toolset plugin installed at one point but have since removed it.

@JorgeB, I reinstalled ZFS Master and was able to destroy 1 of the 2 datasets (disk 12 is fixed, disk 11 is not). It says "disk11/Other: Operation not permitted."

 

So, its a dataset like you said, and I could delete 1 of the 2, but still have one that won't delete.

zfs list -t all output:

 

NAME            USED  AVAIL     REFER  MOUNTPOINT
cache           415G   484G      120K  /mnt/cache
cache/apps      238G   484G      238G  /mnt/cache/apps
cache/data      147G   484G      147G  /mnt/cache/data
cache/docker   30.0G   484G     30.0G  /mnt/cache/docker
cache/domains    96K   484G       96K  /mnt/cache/domains
cache/system   7.75M   484G     7.75M  /mnt/cache/system
disk1          12.4T   149G     12.4T  /mnt/disk1
disk10         12.3T   258G     12.3T  /mnt/disk10
disk11         12.3T   275G      104K  /mnt/disk11
disk11/Other     96K   275G       96K  /mnt/disk11/Other
disk11/data    12.3T   275G     12.3T  /mnt/disk11/data
disk12         12.2T   357G       96K  /mnt/disk12
disk12/data    12.2T   357G     12.2T  /mnt/disk12/data
disk13         12.3T   253G     12.3T  /mnt/disk13
disk14         12.2T   441G      104K  /mnt/disk14
disk14/data    12.2T   441G     12.2T  /mnt/disk14/data
disk2          12.5T   117G     12.5T  /mnt/disk2
disk5          12.2T   427G     12.2T  /mnt/disk5
disk9          12.4T   246G      104K  /mnt/disk9
disk9/data     12.4T   246G     12.4T  /mnt/disk9/data

@JorgeB got it. I renamed the dataset to Other2. That worked. Then I was able to delete it successfully. However, this made it invalid to delete the share as the "directory" was invalid. So I had to hop on my windows box, create a folder on a disk called Other. Then I was able to delete it.

 

Cumbersome, crazy but it worked. haha