systemd 196-2 does not cleanly unmount?

whoop · 2012-11-27 23:55:42

After updating systemd to 196-2 it looks like the system is not being unmounted correctly on my machine:
before:

...
Unmounted /dev/mque
Disabling swaps
Detaching loop devices.
Detaching DM devices.

after update:

...
Unmounted /dev/mque
Unmounted /sys/kernel/debug
Not all filesystems unmounted, 1 left.
Disabling swaps
Detaching loop devices.
Detaching DM devices.
Unmounting file systems
Not all filesystems unmounted, 1 left.
Cannot filnalize remaining file systems and devices, giving up.

Anybody have any ideas? I can't even seem to figure out what filesystems are failing and why...

flipper T · 2012-11-28 00:15:25

I have exactly same issue.

No noticeable "side-effects" though, shutdown seems to proceed from here as expected.

Last edited by flipper T (2012-11-28 00:18:45)

ball · 2012-11-28 10:55:46

For me it's the same issue, too. (On my machine are two devices left mounted, though.) I've had this problem ever since switching to systemd. Until now I didn't experience bad consequences...

koyote · 2012-11-28 13:29:58

Yes, same issue here, in a PC (64 bits) and netbook (32 bits).

nbtrap · 2012-11-28 13:37:38

I'm getting it too. I'm also noticing duplicate entries in my df output, which I'm pretty sure was not the case before this last upgrade:

Filesystem     1K-blocks      Used Available Use% Mounted on
rootfs          22678012  13867116   7658896  65% /
dev              1913920         0   1913920   0% /dev
run              1916776       456   1916320   1% /run
/dev/sda3       22678012  13867116   7658896  65% /
tmpfs            1916776        68   1916708   1% /dev/shm
tmpfs            1916776         0   1916776   0% /sys/fs/cgroup
tmpfs            1916776        16   1916760   1% /tmp
/dev/sda4      284368816 129816244 140107400  49% /home
/dev/sda1          99150     30780     63250  33% /boot

Here's my /etc/fstab:

# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
#devpts                 /dev/pts      devpts    defaults            0      0
#shm                    /dev/shm      tmpfs     nodev,nosuid        0      0
/dev/sda1 /boot ext2 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext4 defaults 0 1
/dev/sda4 /home ext4 defaults 0 1

tomegun · 2012-11-28 14:06:05

To better debug this, make sure you enable the shutdown hook in mkinitcpio.conf, and before rebooting edit /run/initramfs/shutdown and insert a call to '/bin/ash' near the top to give you a debug shell. That should make it possible to at least figure out which partitions are not being cleanly unmonuted, and what process, if any, are staying around preventing the unmount.

PS: you might want to open a bug report once you have some more info so this does not get lost.

Last edited by tomegun (2012-11-28 14:06:35)

awesomenickname · 2012-11-28 17:31:31

Have the same issue.

Arch X86_64, KDE 4.9.3, systemd 196-2

tomegun · 2012-11-28 17:35:27

This was most probably solved by: http://cgit.freedesktop.org/systemd/sys … 04f97e4a98.

The filesystem that is not getting unmounted is almost certainly /, and it is not meant to be unmounted so the error is nothing to worry about. Anything else would have printed a warning with the name of the mountpoint.

To be on the safe side, always use the 'shutdown' hook in your initramfs and that will unmount any remaining filesystems.

R00KIE · 2012-11-28 17:46:33

Everything should be ok

http://i46.tinypic.com/15gqixd.jpg

(1) is when it enters the shutdown hook and (2) is right at the end before the poweroff|shutdown|halt or kexec step.

At (1) the only things still mounted are the rootfs as read only, devpts, cgroups, /sys/fs/cgroup{systemd,cpuset,"cpu,cpuacct",memory,devices,freezer,net_cls.blkio}, /proc and /dev{,shm}. Since I have lvm on luks, both the lvm vg and the luks device will still be open.

At (2) everything seems to be gone (didn't really check, but if it can deactivate the lvm vg then I suppose there is nothing being used).

Either way since the only thing that really matters (the rootfs partition) is already mounted as read only I suppose there would be no harm done.

Last edited by R00KIE (2012-11-28 17:54:49)

awesomenickname · 2012-11-28 18:09:53

Also, when I get this type of error, the system sometimes turning off more 1-2 minutes.

ball · 2012-11-28 20:51:45

For the record: I've been using the shutdown hook for quite some time now -- it doesn't seem to change this problem...

tomegun · 2012-11-28 20:54:41

The warning is harmless. The above commit removes it.

T.J.S. · 2012-11-29 05:13:29

Same issue here.
I added the shutdown hook and the shutdown is almost instant now (just like before the systemd upgrade), but the warning is still there. Before adding the hook, I had to wait 40-50 seconds to see anything happen on the screen, and then the very rapid message sequence began before it shutted down. (with the mentioned warnings)

Even if the warnings are harmless, still, it shouldn't be needed for people to add the hook to make the shutdown faster, right?

tomegun · 2012-11-29 12:17:05

T.J.S. wrote:

Even if the warnings are harmless, still, it shouldn't be needed for people to add the hook to make the shutdown faster, right?

It has been fixed in git, so will go away in the next release.

ackalker · 2012-12-10 03:03:53

When is this fix going to hit [core]?
I'm still seeing this warning as of today (systemd 196-2).

And yes, I've updated my /etc/fstab to the new default (only / and swap in there, no /tmp).

Last edited by ackalker (2012-12-10 03:10:19)

Scimmia · 2012-12-10 03:14:39

Probably when 197 is released. Your guess is as good as anyone's on that.

Arch Linux

#1 2012-11-27 23:55:42

systemd 196-2 does not cleanly unmount?

#2 2012-11-28 00:15:25

Re: systemd 196-2 does not cleanly unmount?

#3 2012-11-28 10:55:46

Re: systemd 196-2 does not cleanly unmount?

#4 2012-11-28 13:29:58

Re: systemd 196-2 does not cleanly unmount?

#5 2012-11-28 13:37:38

Re: systemd 196-2 does not cleanly unmount?

#6 2012-11-28 14:06:05

Re: systemd 196-2 does not cleanly unmount?

#7 2012-11-28 17:31:31

Re: systemd 196-2 does not cleanly unmount?

#8 2012-11-28 17:35:27

Re: systemd 196-2 does not cleanly unmount?

#9 2012-11-28 17:46:33

Re: systemd 196-2 does not cleanly unmount?

#10 2012-11-28 18:09:53

Re: systemd 196-2 does not cleanly unmount?

#11 2012-11-28 20:51:45

Re: systemd 196-2 does not cleanly unmount?

#12 2012-11-28 20:54:41

Re: systemd 196-2 does not cleanly unmount?

#13 2012-11-29 05:13:29

Re: systemd 196-2 does not cleanly unmount?

#14 2012-11-29 12:17:05

Re: systemd 196-2 does not cleanly unmount?

#15 2012-12-10 03:03:53

Re: systemd 196-2 does not cleanly unmount?

#16 2012-12-10 03:14:39

Re: systemd 196-2 does not cleanly unmount?

Board footer