FS#45863 - [linux] "systemctl reboot" never reboots on 223 with lvm, mdadm raid, btrfs raid

Attached to Project: Arch Linux
Opened by Walter Cooks (wlcrls47) - Saturday, 01 August 2015, 20:58 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 15 October 2017, 14:14 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

"systemctl reboot":
[ OK ] Reached target Shutdown.
[ ] watchdog watchdog0: watchdog did not stop!
[ ] watchdog watchdog0: watchdog did not stop!
[ ] cgroup: option or name mismatch, new: 0x0 "", old: 0x4 "systemd"
[ ] shutdown[1]: Failed to finalize DM devices, ignoring
[ ] INFO: task shutdown:1 blocked for more than 120 seconds.
[ ] Not tainted 4.1.3-1-ARCH #1
[ ] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
It then repeats the INFO-echo lines forever with 2 minutes in between each set, until I manually hit the power switch.

Fresh arch install, kernel 4.1.3-1, lvm2 2.02.125-1, mdadm 3.3.2-2
I am running lvm
I have an mdadm raid1 of /dev/md0 for swap of 3 LVM logical volumes
I have a btrfs raid1 of 3 LVM logical volumes
I ran "mdadm --detail --scan > /mountpoint/etc/mdadm.conf" during installation
I added "mdadm_udev lvm2" to /etc/mkinitcpio.conf between "block" and "filesystemd" during installation, then ran "mkinitcpio -p linux"
"dmsetup -ls" properly shows all 3 of my LVM logical volumes
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 15 October 2017, 14:14 GMT
Reason for closing:  No response
Comment by Walter Cooks (wlcrls47) - Sunday, 02 August 2015, 00:03 GMT
upstream systemd says this bug isn't them, but didn't give guidance on what it might be.
Comment by mattia (nTia89) - Monday, 02 October 2017, 20:18 GMT
is this issue still valid?

Loading...