[Bug 1055641] New: Command failed on shutdown phase
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641 Bug ID: 1055641 Summary: Command failed on shutdown phase Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: otuominen@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 738262 --> http://bugzilla.opensuse.org/attachment.cgi?id=738262&action=edit screenshot When shutting down Leap, system is trying to run command which fails. See attached screenshot. I haven't setup any commands which should be run at shutdown. So this is a bug but I cannot track what is causing it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c1
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c2
--- Comment #2 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c3
--- Comment #3 from Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c5
--- Comment #5 from Neil Rickert
I'm wondering how you can deduce from the screenshot that this is happening after all file systems have been unmounted.
I made that comment about "unmounted". It is based on what I see when shutting down Tumbleweed. In my grub boot line, I have removed "splash=silent". So I see lots of boot messages and lots of shutdown messages. When I see that series of "Command failed", I have already seen the unmount messages, including one "failed to unmount" message (which seems an unimportant "bug"). Otherwise, what I see is almost identical to the screenshot, except that the last line is usually "restarting" instead of "powering off". -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c6
Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c7
Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c8
Franck Bui
Is "systemd-analyze set-log-level debug" permanent?
It's not persistent across reboots, if that's what you were asking for. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c9
--- Comment #9 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c10
--- Comment #10 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c11
--- Comment #11 from Franck Bui
- Does the reboot finally happen after waiting a few minutes (at least 3min) ?
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c12
--- Comment #12 from Olli Tuominen
(In reply to Franck Bui from comment #9)
- Does the reboot finally happen after waiting a few minutes (at least 3min) ?
Yes, almost immediately. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c13
--- Comment #13 from Franck Bui
(In reply to Franck Bui from comment #11)
(In reply to Franck Bui from comment #9)
- Does the reboot finally happen after waiting a few minutes (at least 3min) ?
Yes, almost immediately.
I meant when doing "systemctl shutdown" or "shutdown" (without the '-f' switch). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c14
--- Comment #14 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c15
--- Comment #15 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c16
--- Comment #16 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c17
--- Comment #17 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c18
--- Comment #18 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c19
--- Comment #19 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c20
--- Comment #20 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c21
--- Comment #21 from Neil Rickert
OK so apparently there's something wrong with /dev/dm-0
Since I reported seeing the same sort of messages with Tumbleweed, I'll comment here. I use an encrypted LVM. And "/dev/dm-0" is the access to that LVM. Inside the LVM, I have volumes "root1", "root2", "root3", "swap", "home". I use "ext4" for home and root. If the root file system is the "root1" volume, then the "home" volume is mounted at "/home". If the root file system is either the "root2" or "root3" volume, then the "home" volume is mounted at "/xhome". The shutdown messages seem to show the crypto being properly undone. And that happens before the "Command failed" messages show up. If I mount the "home" volume at "/xhome", then I usually see a message "Failed to unmount /xhome". I have checked by booting rescue media, and that file system shows as clean. So I think it fails to unmount it because it has already unmounted it, though I cannot see where. If I have given more detail than is relevant, please ignore that extra detail. Hmm, here's another point I should mention. I also have Tumbleweed on a spare partition on a laptop. In that case, the root file system is "/dev/sda8" and is not encrypted at all. But I do still mount "home" from the encrypted LVM at "/xhome" and I still use swap from the encrypted LVM. On that system, I still get the "Command failed" messages on shutdown. And I still see the "failed to unmount /xhome" (before the "Command failed"). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c22
--- Comment #22 from Franck Bui
Hmm, here's another point I should mention. I also have Tumbleweed on a spare partition on a laptop. In that case, the root file system is "/dev/sda8" and is not encrypted at all. But I do still mount "home" from the encrypted LVM at "/xhome" and I still use swap from the encrypted LVM. On that system, I still get the "Command failed" messages on shutdown. And I still see the "failed to unmount /xhome" (before the "Command failed").
In this case could you try to follow the procedure in comment #14 to see if you can get more destails with dmesg ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c23
--- Comment #23 from Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c24
Franck Bui
I'm guessing that the "watchdog did not stop" is related to the "Command failed" messages.
Daniel, it seems that those messages are emitted by dracut once systemd completed its shutdown sequence and gave the control to /shutdown script. Do you have an idea about those "Command failed" messages ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c25
--- Comment #25 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c26
--- Comment #26 from Franck Bui
OK so apparently there's something wrong with /dev/dm-0.
After some research it appears that the warnings: systemd-shutdown[1]: Detaching DM 254:0. systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Not all DM devices detached, 1 left. are emitted because we're trying to detach the device that contains the rootfs. And this is doomed to fail as we're currently using it. Normally we should detect this case and skip detaching the DM device hosting the rootfs but in your case BTRFS is used and the detection was failing. I submitted a patch to fix that: https://github.com/systemd/systemd/pull/6811 However the original issue remains... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c27
--- Comment #27 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c28
--- Comment #28 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c29
--- Comment #29 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c30
--- Comment #30 from Franck Bui
So I did a set -x to /usr/lib/dracut/modules.d/90dm/dm-shutdown.sh
Did you recreated the initrd at that point (by running mkinitrd) ?
Rebooted and used "plymouth..." for booting option. Did C#14 and rebooted.
Attached the journalctl after rebooting.
Nothing interesting is supposed to be recorded in the journal since all happens when journald is off... only on the console or in dmesg. BTW can you still see the "Command failed" messages ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c31
--- Comment #31 from Olli Tuominen
Did you recreated the initrd at that point (by running mkinitrd) ?
Now I did and there is so much messages and so fast that I cannot follow them.
Nothing interesting is supposed to be recorded in the journal since all happens when journald is off... only on the console or in dmesg.
ok -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c32
--- Comment #32 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c33
Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c34
--- Comment #34 from Franck Bui
ok - so I got following:
... ++ devname=system-root ++ dmsetup -v --noudevsync remove system-root Command failed
Good we at least spotted the command that fails... What if you manually try to execute the failing command in the debug shell spawned by dracut ? Can you see more messages ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c35
--- Comment #35 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c36
--- Comment #36 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c37
--- Comment #37 from Daniel Molkentin
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c38
--- Comment #38 from Franck Bui
Can you prefix the command with "strace -f" and attach the output (goes to stderr by default)?
I think you should explain how to embed strace in the initrd as it's not really obvious. Also if a (shutdown) hook fails, couldn't dracut emit a warning which includes the name of the hook or the relevant module ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c39
--- Comment #39 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c40
--- Comment #40 from Thomas Blume
I check with lsof dm-0 but it didn't show anything.
Might be good to get the status of the lv, can you please edit: /usr/lib/dracut/modules.d/90dm/dm-shutdown.sh and just before the row: dmsetup -v --noudevsync remove "$devname" || return $? put: dmsetup info -v "$devname" ? Afterwards please recreate the initrd (you might want to backup the old one before) and reproduce the issue. The console output should show the status of the lv, just before removal. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c41
--- Comment #41 from Olli Tuominen
put:
dmsetup info -v "$devname"
? Afterwards please recreate the initrd (you might want to backup the old one before) and reproduce the issue. The console output should show the status of the lv, just before removal.
is it possible to setup brake point that I could take a screenshot or such? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c42
--- Comment #42 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c43
Thomas Blume
Created attachment 740630 [details] reply for C#41
dmsetup info
Hm: Open count: 1 State: ACTIVE Apparently this is an active logical volume. I'm not sure whether is the proper way to remove the dm table for an lv without notifying lvm. Daniel, do you know why upstream didn't just do a lvchange -an? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c44
--- Comment #44 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c45
--- Comment #45 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c46
--- Comment #46 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c47
--- Comment #47 from Franck Bui
Created attachment 740651 [details] screenshot of cat /proc/mounts
Thanks Olli but you ran the command when you break at the "pre-shutdown" phase, see the shell prompt which is "pre-shutdown:/#" I was interested to run the commands at the "shutdown" phase/step. You normally should break there once you exited from the "pre-shutdown" debug shell since you normmally did: # echo "rd.debug rd.break=pre-shutdown rd.break=shutdown" > /run/initramfs/etc/cmdline.d/debug.conf as indicated in comment #14. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c48
--- Comment #48 from Franck Bui
Once I unmounted that /oldroot I was able to execute "dmsetup -v --noudevsync remove system-root" command
It seems to be somekind of snapshot of the root fs?
Huh ? you were able to umount /oldroot yourself without any error ? That would mean that dracut skips the unmount command entirely for some reasons in your case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c49
--- Comment #49 from Olli Tuominen
Huh ? you were able to umount /oldroot yourself without any error ?
That is true.
That would mean that dracut skips the unmount command entirely for some reasons in your case.
Can it be timing issue? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c50
--- Comment #50 from Franck Bui
Can it be timing issue?
I don't think so as everything is executed sequentially during the shutdown process of dracut. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c51
--- Comment #51 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c52
--- Comment #52 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c53
--- Comment #53 from Franck Bui
Just to verify that my 54 line starts with _cnt=0
and before it I'll put set -x exec 2>/dev/kmsg ?
Yes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c54
--- Comment #54 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c55
--- Comment #55 from Franck Bui
So today came the dracut patch - and it seems to fix it (something).
There's no actual patch/fix, but only 2 commands added to the shutdown script to enable debug logs...
At least I did just reboot and I didn't see the message(s) anymore.
Of course since stderr has been redirected to /dev/kmsg.
The /oldroot is mounted on <pre-shutdown> stage but when I <Ctrl>-d to <shutdown> stage it has disappeared.
I copied <pre-shutdown> dmesg to /oldroot/tmp/ but I cannot find it from the /tmp/ now. Is it actually a snapshot?
You were asked to copy the output of dmesg in /oldroot, not in /oldroot/tmp... Can you please follow the instructions and provide the output of dmesg ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c56
--- Comment #56 from Olli Tuominen
The /oldroot is mounted on <pre-shutdown> stage but when I <Ctrl>-d to <shutdown> stage it has disappeared.
I copied <pre-shutdown> dmesg to /oldroot/tmp/ but I cannot find it from the /tmp/ now. Is it actually a snapshot?
You were asked to copy the output of dmesg in /oldroot, not in /oldroot/tmp...
Can you please follow the instructions and provide the output of dmesg ?
Can you provide instructions how to do so as in shutdown stage there is no more /oldroot I can only do it in pre-shutdown when /oldroot is still mounted. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c57
--- Comment #57 from Franck Bui
Can you provide instructions how to do so as in shutdown stage there is no more /oldroot
I can only do it in pre-shutdown when /oldroot is still mounted.
Then the assumption of /oldroot being still mounted was wrong. Please at the *shutdown* stage, issue the following command: - cat /proc/mounts - dmsetup info -v system-root Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c58
--- Comment #58 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c59
--- Comment #59 from Olli Tuominen
Please at the *shutdown* stage, issue the following command:
- cat /proc/mounts
missing the /oldroot
- dmsetup info -v system-root
Device does not exist -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c60
--- Comment #60 from Franck Bui
(In reply to Franck Bui from comment #57)
Please at the *shutdown* stage, issue the following command:
- cat /proc/mounts
missing the /oldroot
- dmsetup info -v system-root
Device does not exist
I'm puzzled... According to your comment #32, "dmsetup remove" is supposed to the failing command. And this command is executed by lib/dracut/hooks/shutdown/25-dm-shutdown.sh. In its turn this script is supposed to be called between "pre-shutdown" and "shutdown" by /shutdown. Can you comment the changes in /usr/lib/dracut/modules.d/99shutdown/shutdown.sh requested in comment #51, recreate the initrd and retry ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c61
--- Comment #61 from Neil Rickert
So I think I'll test boot couple of times and if Neil Rickert hasn't encounter >issues anymore we can close this.
I'm out of town at present, so not easily able to test. Feel free to close the bug without my feedback, if you believe you have it resolved. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c62
--- Comment #62 from Olli Tuominen
I'm puzzled...
According to your comment #32, "dmsetup remove" is supposed to the failing command. And this command is executed by lib/dracut/hooks/shutdown/25-dm-shutdown.sh.
Yep, I did the change to C#29 (included sleep so got that message out)
In its turn this script is supposed to be called between "pre-shutdown" and "shutdown" by /shutdown.
Can you comment the changes in /usr/lib/dracut/modules.d/99shutdown/shutdown.sh requested in comment #51, recreate the initrd and retry ?
I'll attach two pic which systemd-shutdown fails to unmount but /shutdown is able to do so. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c63
--- Comment #63 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c64
--- Comment #64 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c65
--- Comment #65 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c67
Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c69
--- Comment #69 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c70
--- Comment #70 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c71
--- Comment #71 from Franck Bui
Of course there is "killing all remain processes" between systemd-shutdown | shutdown: can this release lock to unmount system-root?
That could be indeed a possibility... Ok last try: - please create the following script:
# cat foo.sh #!/bin/bash
for p in /proc/[0-9]*; do for l in $(ls -l $p/ $p/fd 2>/dev/null); do case $l in *$1*) printf "%s: %s\n" $(< $p/comm) $(< $p/cmdline) esac done done
- make it executable : chmod +x foo.sh - include it in the initramfs: "mkinitrd --install $(pwd)/foo.sh" (make sure to use an absolute path with --install otherwise dracut will silently ignore the option :-/) - make sure the script has been included : "lsinitrd | grep foo" - break in the *pre-shutdown* step - execute the script: "/root/foo.sh /oldroot" (assuming that the script was initially created in /root - please post the result of the script (if any) Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c72
--- Comment #72 from Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c73
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c74
Olli Tuominen
@Olli, could you test the procedure given in comment #71 without updating your system for now ?
Nope. It didn't print anything. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c75
--- Comment #75 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c89
--- Comment #89 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c90
--- Comment #90 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c91
--- Comment #91 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c92
--- Comment #92 from Olli Tuominen
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c93
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641#c100
--- Comment #100 from Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1055641
Michiel Janssens
participants (1)
-
bugzilla_noreply@novell.com