September 25, 20232 yr This has happened both times I've tried to restart the array since upgrading to 6.12.4, and changing my two pools from BTRFS to ZFS. Syslog: Sep 25 08:44:09 server emhttpd: shcmd (2559484): /usr/sbin/zpool export ssd Sep 25 08:44:09 server root: cannot unmount '/mnt/ssd': pool or dataset is busy Sep 25 08:44:09 server emhttpd: shcmd (2559484): exit status: 1 Sep 25 08:44:09 server emhttpd: Retry unmounting disk share(s)... Sep 25 08:44:14 server emhttpd: Unmounting disks... Sep 25 08:44:14 server emhttpd: shcmd (2559485): /usr/sbin/zpool export ssd Sep 25 08:44:14 server root: cannot unmount '/mnt/ssd': pool or dataset is busy Sep 25 08:44:14 server emhttpd: shcmd (2559485): exit status: 1 Sep 25 08:44:14 server emhttpd: Retry unmounting disk share(s)... Sep 25 08:44:19 server emhttpd: Unmounting disks... I tried to unmount /mnt/ssd/ as well as forcibly, but no luck. I'd post diags, but they seem to be stuck collecting (10+ mins now) Any output I can get on this before I force it down? Edited September 25, 20232 yr by -Daedalus
September 25, 20232 yr Author For anyone looking at this in future: I ended up forcing it down. The only thing I could think of still running is the syslog server. It was writing to a dataset on the 'ssd' pool. When the server came back up, that share was on the array.
September 25, 20232 yr I have problems with the same config too. The System becomes unresponsive, smb-connection not possible. The VMs run smoothly though. Even cli on the machine itself cannot shut the system down, so hard-reset is the only possibility. After that the server runs a few days without any issues and then it starts again.
September 25, 20232 yr Community Expert 2 hours ago, -Daedalus said: but they seem to be stuck collecting (10+ mins now) If it happens again post the output of losetup and post the syslog: cp /var/log/syslog /boot/syslog.txt
September 25, 20232 yr Author I actually did this because I found another one of your answers to a similar issue. It was, I think, this: NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /boot/bzfirmware 0 512 /dev/loop0 0 0 1 1 /boot/bzmodules 0 512 Or, at least, these were the two files listed. The values may have differed. fwiw
September 25, 20232 yr Community Expert That looks OK, and it means docker and libvirt images were not mounted, so not the reason.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.