Bug#688985: systemd: Shutdown hangs when block devices are blocked
On Tue, Dec 24, 2013 at 03:36:51PM +0100, Tollef Fog Heen wrote: Am Dienstag, den 21.05.2013, 18:44 +0200 schrieb Michael Biebl: Am 21.05.2013 17:25, schrieb Paul Menzel: - Is this problem reproducible? What are the steps to reproduce the problem? Yes. Just shut down the system with `sudo halt` for example. Ahem, halt under systemd does *not* power off the machine, that is expected. This is actually a bug in sysvinit, that it does power off. Interesting. I did not know that. Use poweroff or halt -p if you want that behaviour. `halt -p` indeed powered the machine off. So it now works just fine when you're using halt -p/shutdown -h and I can close the bug, or are you still experiencing problems? I guess this bug could be closed. Just migrated from sysvinit to systemd, this is always reproducible for me: 'poweroff': system powered off. 'halt': system halted, not powered off. So these commands now really do what their names promise to do. Wolfgang signature.asc Description: Digital signature
Bug#688985: systemd: Shutdown hangs when block devices are blocked
]] Paul Menzel Hi, sorry for not getting back to you earlier. Am Dienstag, den 21.05.2013, 18:44 +0200 schrieb Michael Biebl: Am 21.05.2013 17:25, schrieb Paul Menzel: - Is this problem reproducible? What are the steps to reproduce the problem? Yes. Just shut down the system with `sudo halt` for example. Ahem, halt under systemd does *not* power off the machine, that is expected. This is actually a bug in sysvinit, that it does power off. Interesting. I did not know that. Use poweroff or halt -p if you want that behaviour. `halt -p` indeed powered the machine off. So it now works just fine when you're using halt -p/shutdown -h and I can close the bug, or are you still experiencing problems? Cheers, -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688985: systemd: Shutdown hangs when block devices are blocked
Am Dienstag, den 21.05.2013, 18:44 +0200 schrieb Michael Biebl: Am 21.05.2013 17:25, schrieb Paul Menzel: - Is this problem reproducible? What are the steps to reproduce the problem? Yes. Just shut down the system with `sudo halt` for example. Ahem, halt under systemd does *not* power off the machine, that is expected. This is actually a bug in sysvinit, that it does power off. Interesting. I did not know that. Use poweroff or halt -p if you want that behaviour. `halt -p` indeed powered the machine off. Thanks and sorry for the noise, Paul signature.asc Description: This is a digitally signed message part
Bug#688985: systemd: Shutdown hangs when block devices are blocked
Dear Michael, dear Matthias, Am Samstag, den 17.11.2012, 03:04 +0100 schrieb Michael Biebl: Hi, On 27.09.2012 23:06, Matthias Urlichs wrote: My shutdown ends with these lines: Not all DM devices detached, 3 left Cannot finalize remaining file systems and devices, giving up. ... and it hangs there. I had an accidentally unplugged USB disk, but that shouldn't block a reboot. I think, I am seeing the same problem with Debian Wheezy. But after Not all DM devices detached, 1 left Cannot finalize remaining file systems and devices, giving up. I see `System halted` (or halt not sure) at the end and the system just does not turn off. It worked fine with the package sysvinit. Although there I got a fail message due to the encrypted device too. But it went on, I saw `system halted` and it turned off. I need more information how to reproduce the issue. - Could you post your /etc/fstab $ more /etc/fstab # /dev/sda2crypt UUID=f198e82a-32df-4f18-bec0-3e08802b084d / auto defaults,errors=remount-ro,discard 0 1 # /dev/sda1 UUID=4843f52e-f13a-4f3f-a105-a91ca427dbd8 /boot auto defaults,discard0 1 proc /procprocdefaults 0 0 /dev/cdrom /mnt/cdrom0 iso9660 ro,user,noauto0 0 $ more /mnt/etc/crypttab # target name source device key file options sda2cryptUUID=2ccdecd7-afe8-417f-87cb-4bf23ab7d9f7 none luks,discard - Is this problem reproducible? What are the steps to reproduce the problem? Yes. Just shut down the system with `sudo halt` for example. - Do you use LVM/device-mapper/cryptsetup? I am using cryptsetup. Thanks, Paul signature.asc Description: This is a digitally signed message part
Bug#688985: systemd: Shutdown hangs when block devices are blocked
Am 21.05.2013 17:25, schrieb Paul Menzel: - Is this problem reproducible? What are the steps to reproduce the problem? Yes. Just shut down the system with `sudo halt` for example. Ahem, halt under systemd does *not* power off the machine, that is expected. This is actually a bug in sysvinit, that it does power off. Use poweroff or halt -p if you want that behaviour. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#688985: systemd: Shutdown hangs when block devices are blocked
Hi, On 27.09.2012 23:06, Matthias Urlichs wrote: My shutdown ends with these lines: Not all DM devices detached, 3 left Cannot finalize remaining file systems and devices, giving up. ... and it hangs there. I had an accidentally unplugged USB disk, but that shouldn't block a reboot. I need more information how to reproduce the issue. - Could you post your /etc/fstab - Is this problem reproducible? What are the steps to reproduce the problem? - Do you use LVM/device-mapper/cryptsetup? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#688985: systemd: Shutdown hangs when block devices are blocked
Package: systemd Version: 44-4 Severity: important My shutdown ends with these lines: Not all DM devices detached, 3 left Cannot finalize remaining file systems and devices, giving up. ... and it hangs there. I had an accidentally unplugged USB disk, but that shouldn't block a reboot. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), (550, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii dpkg 1.16.8 ii initscripts 2.88dsf-31 ii libacl1 2.2.51-8 ii libaudit01:1.7.18-1.1 ii libc62.13-35 ii libcap2 1:2.22-1 ii libcryptsetup4 2:1.4.3-2 ii libdbus-1-3 1.6.0-1 ii libkmod2 9-1 ii liblzma5 5.1.1alpha+20120614-1 ii libpam0g 1.1.3-7.1 ii libselinux1 2.1.9-5 ii libsystemd-daemon0 44-4 ii libsystemd-id128-0 44-4 ii libsystemd-journal0 44-4 ii libsystemd-login044-4 ii libudev0 175-7 ii libwrap0 7.6.q-24 ii udev 175-7 ii util-linux 2.20.1-5.1 Versions of packages systemd recommends: ii libpam-systemd 44-4 Versions of packages systemd suggests: ii python2.7.3~rc2-1 ii python-cairo 1.8.8-1+b2 ii python-dbus 1.1.1-1 pn systemd-gui none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
