After the latest Nov 6th testing branch update, I’ve started getting unmount errors when shutting down or restarting the system. I’m on the 5.9.6 kernel.
The volumes failing are
/home/owen/Backups
/home
/tmp
Here's the relevent part of the log:
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounting /boot/efi...
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounting /boot/images...
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounting /home/owen/Backups...
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounting /home/owen/Downloads...
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounting /home/owen/Work...
Nov 09 01:20:50 twifty-lynx umount[5227]: umount: /home/owen/Backups: target is busy.
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounting /run/timeshift/backup...
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounting Temporary Directory (/tmp)...
Nov 09 01:20:50 twifty-lynx umount[5231]: umount: /tmp: target is busy.
Nov 09 01:20:50 twifty-lynx systemd[1]: boot-efi.mount: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounted /boot/efi.
Nov 09 01:20:50 twifty-lynx systemd[1]: home-owen-Backups.mount: Mount process exited, code=exited, status=32/n/a
Nov 09 01:20:50 twifty-lynx systemd[1]: Failed unmounting /home/owen/Backups.
Nov 09 01:20:50 twifty-lynx kernel: fbcon: Taking over console
Nov 09 01:20:50 twifty-lynx kernel: Console: switching to colour frame buffer device 160x45
Nov 09 01:20:50 twifty-lynx systemd[1]: boot-images.mount: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounted /boot/images.
Nov 09 01:20:50 twifty-lynx systemd[1]: home-owen-Work.mount: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounted /home/owen/Work.
Nov 09 01:20:50 twifty-lynx systemd[1]: run-timeshift-backup.mount: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Unmounted /run/timeshift/backup.
Nov 09 01:20:50 twifty-lynx systemd[1]: tmp.mount: Mount process exited, code=exited, status=32/n/a
Nov 09 01:20:50 twifty-lynx systemd[1]: Failed unmounting Temporary Directory (/tmp).
Nov 09 01:20:50 twifty-lynx systemd[1]: Stopped target Swap.
Nov 09 01:20:50 twifty-lynx systemd[1]: Deactivating swap /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_1TB_S467NF0K607683A-part19...
Nov 09 01:20:50 twifty-lynx systemd[1]: systemd-fsck@dev-disk-by\x2duuid-3e8dba90\x2d8801\x2d46e9\x2d8198\x2d8755170a5174.service: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Stopped File System Check on /dev/disk/by-uuid/3e8dba90-8801-46e9-8198-8755170a5174.
Nov 09 01:20:50 twifty-lynx systemd[1]: systemd-fsck@dev-disk-by\x2duuid-67ce9ede\x2d2aac\x2d49c3\x2db102\x2d501ee6a107bc.service: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Stopped File System Check on /dev/disk/by-uuid/67ce9ede-2aac-49c3-b102-501ee6a107bc.
Nov 09 01:20:50 twifty-lynx systemd[1]: systemd-fsck@dev-disk-by\x2duuid-87F2\x2dB10A.service: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Stopped File System Check on /dev/disk/by-uuid/87F2-B10A.
Nov 09 01:20:50 twifty-lynx systemd[1]: systemd-fsck@dev-disk-by\x2duuid-fc8f9007\x2d6ed1\x2d47cc\x2dbc6d\x2d7f7455829527.service: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Stopped File System Check on /dev/disk/by-uuid/fc8f9007-6ed1-47cc-bc6d-7f7455829527.
Nov 09 01:20:50 twifty-lynx systemd[1]: dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_1TB_S467NF0K607683A\x2dpart19.swap: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Deactivated swap /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_1TB_S467NF0K607683A-part19.
Nov 09 01:20:50 twifty-lynx systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart19.swap: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:01:00.0-nvme-1-part19.
Nov 09 01:20:50 twifty-lynx systemd[1]: dev-disk-by\x2did-nvme\x2deui.0025385681b0c084\x2dpart19.swap: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Deactivated swap /dev/disk/by-id/nvme-eui.0025385681b0c084-part19.
Nov 09 01:20:50 twifty-lynx systemd[1]: dev-disk-by\x2dpartuuid-c5e8359d\x2df1c1\x2d472f\x2d8867\x2da500b3fac803.swap: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Deactivated swap /dev/disk/by-partuuid/c5e8359d-f1c1-472f-8867-a500b3fac803.
Nov 09 01:20:50 twifty-lynx systemd[1]: dev-nvme0n1p19.swap: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Deactivated swap /dev/nvme0n1p19.
Nov 09 01:20:50 twifty-lynx systemd[1]: dev-disk-by\x2duuid-3d4d6a4f\x2db96c\x2d4a9c\x2d9aa1\x2dca287b1f1d3e.swap: Succeeded.
Nov 09 01:20:50 twifty-lynx systemd[1]: Deactivated swap /dev/disk/by-uuid/3d4d6a4f-b96c-4a9c-9aa1-ca287b1f1d3e.
Nov 09 01:20:53 twifty-lynx systemd[1]: home-owen-Downloads.mount: Succeeded.
Nov 09 01:20:53 twifty-lynx systemd[1]: Unmounted /home/owen/Downloads.
Nov 09 01:20:53 twifty-lynx systemd[1]: Unmounting /home...
Nov 09 01:20:53 twifty-lynx systemd[1]: systemd-fsck@dev-disk-by\x2duuid-dd3a7df3\x2dd17c\x2d4e5f\x2db510\x2d3f9073b580bc.service: Succeeded.
Nov 09 01:20:53 twifty-lynx systemd[1]: Stopped File System Check on /dev/disk/by-uuid/dd3a7df3-d17c-4e5f-b510-3f9073b580bc.
Nov 09 01:20:53 twifty-lynx umount[5239]: umount: /home: target is busy.
Nov 09 01:20:53 twifty-lynx systemd[1]: home.mount: Mount process exited, code=exited, status=32/n/a
Nov 09 01:20:53 twifty-lynx systemd[1]: Failed unmounting /home.
Nov 09 01:20:53 twifty-lynx systemd[1]: Reached target Unmount All Filesystems.
My fstab looks like:
UUID=e736e3e9-af77-4679-9afe-05259ef583f6 / ext4 defaults,noatime 0 1
UUID=e6b002fa-33a6-4ade-bb96-fa3bb24c8692 /home ext4 defaults,noatime 0 2
UUID=dd3a7df3-d17c-4e5f-b510-3f9073b580bc /home/owen/Downloads ext4 defaults,noatime 0 2
UUID=fc8f9007-6ed1-47cc-bc6d-7f7455829527 /home/owen/Backups ext4 defaults,noatime 0 2
UUID=67ce9ede-2aac-49c3-b102-501ee6a107bc /home/owen/Work ext4 defaults,noatime 0 2
UUID=3e8dba90-8801-46e9-8198-8755170a5174 /boot/images ext4 defaults,noatime 0 2
UUID=3d4d6a4f-b96c-4a9c-9aa1-ca287b1f1d3e swap swap defaults,noatime 0 2
The very last line of the log states:
Nov 09 01:20:55 twifty-lynx python[3431]: backintime (owen/1): INFO: Resume process "rsync -a --delete /tmp/tmpxdb8leto/ /home/owen/Backups/home/backintime/twifty-lynx/owen/1/20200908-120002-181"
And given the names of the volumes failing to unmount, it appears that backintime could be causing the issue. Obviously I don’t want filesystem errors do to unmount failures followed by a shutdown. Is there anything I need to worry about or any way to fix it?