Your message dated Wed, 31 Oct 2018 22:42:34 +0800
with message-id <[email protected]>
and subject line Re: Bug#826788: fsck run before unmounting?; failed unmounting
/home.
has caused the Debian Bug report #826788,
regarding fsck run before unmounting?; failed unmounting /home.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
826788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826788
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 230-2
Here we see fsck is apparently run _before_ unmounting file systems.
And maybe that is why we see
Failed unmounting /home?
Also there is a Failed unmounting /tmp I can send if you are interested.
# ls -lR /dev/disk/|grep 9405199517
lrwxrwxrwx 1 root root 10 06-09 11:45 355d426a-cbfc-4faf-91d6-4f9405199517 ->
../../sda6
# mount|grep sda6
/dev/sda6 on /home type ext4 (rw,relatime,commit=111,data=ordered)
# egrep /home\|4f9405199517 /shutdown-log.txt
[ 2283.119012] systemd[1]:
systemd-fsck@dev-disk-by\x2duuid-355d426a\x2dcbfc\x2d4faf\x2d91d6\x2d4f9405199517.service:
Installed new job
systemd-fsck@dev-disk-by\x2duuid-355d426a\x2dcbfc\x2d4faf\x2d91d6\x2d4f9405199517.service/stop
as 293
[ 2284.362447] systemd[1]: home.mount: About to execute: /bin/umount /home
[ 2284.363088] systemd[1]: Unmounting /home...
[ 2284.368330] systemd[1846]: home.mount: Executing: /bin/umount /home
[ 2284.422580] systemd[1]: Failed unmounting /home.
[ 2284.451706] systemd[1]: Got cgroup empty notification for:
/system.slice/home.mount
[ 2284.451805] systemd[1]: Got cgroup empty notification for:
/system.slice/home.mount
[ 2284.468145] systemd[1]:
systemd-fsck@dev-disk-by\x2duuid-355d426a\x2dcbfc\x2d4faf\x2d91d6\x2d4f9405199517.service:
Changed exited -> dead
[ 2284.468175] systemd[1]:
systemd-fsck@dev-disk-by\x2duuid-355d426a\x2dcbfc\x2d4faf\x2d91d6\x2d4f9405199517.service:
Job
systemd-fsck@dev-disk-by\x2duuid-355d426a\x2dcbfc\x2d4faf\x2d91d6\x2d4f9405199517.service/stop
finished, result=done
[ 2284.468199] systemd[1]: Stopped File System Check on
/dev/disk/by-uuid/355d426a-cbfc-4faf-91d6-4f9405199517.
[ 2284.786804] systemd[1]:
dev-disk-by\x2duuid-355d426a\x2dcbfc\x2d4faf\x2d91d6\x2d4f9405199517.device:
Failed to send unit remove signal for
dev-disk-by\x2duuid-355d426a\x2dcbfc\x2d4faf\x2d91d6\x2d4f9405199517.device:
Transport endpoint is not connected
[ 2284.793669] systemd[1]:
systemd-fsck@dev-disk-by\x2duuid-355d426a\x2dcbfc\x2d4faf\x2d91d6\x2d4f9405199517.service:
Failed to send unit remove signal for
systemd-fsck@dev-disk-by\x2duuid-355d426a\x2dcbfc\x2d4faf\x2d91d6\x2d4f9405199517.service:
Transport endpoint is not connected
[ 2284.888398] systemd-shutdown[1]: Remounting '/home' read-only with options
'commit=111,data=ordered'.
[ 2285.086788] systemd-shutdown[1]: Unmounting /home.
/var is also on its own partition, but umount succeeds.
# mount|grep /dev/sda
/dev/sda8 on / type ext4 (rw,relatime,errors=remount-ro,commit=111,data=ordered)
/dev/sda7 on /var type ext4 (rw,relatime,commit=111,data=ordered)
/dev/sda6 on /home type ext4 (rw,relatime,commit=111,data=ordered)
# mount|grep /tmp
tmpfs on /tmp type tmpfs (rw,relatime)
I made the log via
# set /lib/systemd/system-shutdown/debug.sh; ls -l $@; cat $@
-rwxr-xr-x 1 root root 80 06-07 21:24 /lib/systemd/system-shutdown/debug.sh
#!/bin/sh
mount -o remount,rw /
dmesg > /shutdown-log.txt
mount -o remount,ro /
# sed s/.*sys/sys/ /proc/cmdline
systemd.log_target=kmsg log_buf_len=10M enforcing=0
--- End Message ---
--- Begin Message ---
OK I haven't noticed it recently. Closing.
--- End Message ---
