October 10, 20232 yr So I added a new disk to my server and it did not detect it so I though I would shut down the Array and restart the server to see if it needed a reboot to find it, and I now cannot shut the array down This is what i see in the log Oct 10 18:07:03 fallout kernel: Oct 10 18:07:03 fallout root: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover stop Oct 10 18:07:07 fallout emhttpd: shcmd (2752742): /usr/sbin/zfs unmount -a Oct 10 18:07:07 fallout emhttpd: shcmd (2752743): umount /mnt/user Oct 10 18:07:07 fallout root: umount: /mnt/user: target is busy. Oct 10 18:07:07 fallout emhttpd: shcmd (2752743): exit status: 32 Oct 10 18:07:07 fallout emhttpd: shcmd (2752744): rmdir /mnt/user Oct 10 18:07:07 fallout root: rmdir: failed to remove '/mnt/user': Device or resource busy Oct 10 18:07:07 fallout emhttpd: shcmd (2752744): exit status: 1 I can see there is a Move process running, but I cannot kill the process. Mover was not running and I have the mover tuning script disabled. Kill -9 does not error and does not stop it. Does anyone know how I can kill it to shut the array down cleanly? root@fallout:~# ps -ef |grep /mnt/user root 2760 18190 0 18:13 pts/1 00:00:00 grep /mnt/user root 11719 1 5 Sep28 ? 16:35:34 /usr/local/bin/shfs /mnt/user -disks 63 -o default_permissions,allow_other,noatime -o remember=330 root@fallout:~# lsof | grep /mnt/user move 6318 root 8r DIR 0,46 4096 18302628885633695872 /mnt/user root@fallout:~# fallout-diagnostics-20231010-2225.zip Edited October 10, 20232 yr by hwextreme
October 10, 20232 yr Author I see the move process has them all open. root@fallout:~# fuser -mv /mnt/disk* /mnt/user/* USER PID ACCESS COMMAND /mnt/disk1: root kernel mount /mnt/disk1 /mnt/disk2: root kernel mount /mnt/disk2 /mnt/disk3: root kernel mount /mnt/disk3 /mnt/disk4: root kernel mount /mnt/disk4 /mnt/disk5: root kernel mount /mnt/disk5 /mnt/disks: root kernel mount /mnt/disks /mnt/user/APPS: root kernel mount /mnt/user root 6318 f.... move /mnt/user/Data: root kernel mount /mnt/user root 6318 f.... move /mnt/user/Docker: root kernel mount /mnt/user root 6318 f.... move /mnt/user/EBooks: root kernel mount /mnt/user root 6318 f.... move /mnt/user/Games: root kernel mount /mnt/user root 6318 f.... move /mnt/user/Movies: root kernel mount /mnt/user root 6318 f.... move /mnt/user/Photos: root kernel mount /mnt/user root 6318 f.... move /mnt/user/TV: root kernel mount /mnt/user root 6318 f.... move /mnt/user/VeeamBackup: root kernel mount /mnt/user root 6318 f.... move /mnt/user/appdata: root kernel mount /mnt/user root 6318 f.... move /mnt/user/appdata-backups: root kernel mount /mnt/user root 6318 f.... move root@fallout:~# root@fallout:~# ps -ef |grep move root 6318 1 0 Sep28 ? 00:00:00 /usr/local/sbin/move -d 1 root 27696 18190 0 18:34 pts/1 00:00:00 grep move root@fallout:~# Little more digging root@fallout:~# umount -a umount: /mnt/user: target is busy. ^[[Aumount: /mnt/disk2: target is busy. umount: /mnt: target is busy. umount: /var/log: target is busy. umount: /sys/fs/cgroup: target is busy. umount: /sys/fs/cgroup: target is busy. umount: /dev: target is busy. umount: /usr: target is busy. umount: /usr: target is busy. umount: /lib: target is busy. umount: /lib: target is busy. umount: /boot: target is busy. umount: /run: target is busy. umount: /: not mounted. root@fallout:~# fuser -mvk /mnt/disk2 USER PID ACCESS COMMAND /mnt/disk2: root kernel mount /mnt/disk2 Edited October 10, 20232 yr by hwextreme
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.