[opensuse] lvm boot fails with timeout in multipath
Boot with LVM root often fails on oS 13.2, and dracut starts the emergency shell. The messages beforehand are (copied with errors): timeout /sbin/multipath -i -u sda1 [slow multipath etc] dracut -initqueue PARTIAL MODE Incomplete logical volumes will be processed [another error message about a missing LVM partition] This issue looks similar to the one described in this[1] Ubuntu bug report. Has anyone else seen this? -------- [1] https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1431650 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Отправлено с iPhone
28 сент. 2015 г., в 8:50, auxsvr <auxsvr@gmail.com> написал(а):
Boot with LVM root often fails on oS 13.2, and dracut starts the emergency shell. The messages beforehand are (copied with errors):
timeout /sbin/multipath -i -u sda1
Do you really need multipath? Then you probably need to give more details about your configuration. It is rather unusual on consumer grade systems.
[slow multipath etc] dracut -initqueue PARTIAL MODE Incomplete logical volumes will be processed [another error message about a missing LVM partition]
This issue looks similar to the one described in this[1] Ubuntu bug report. Has anyone else seen this?
-------- [1] https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1431650
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 28 of September 2015 09:26:35 Andrei Borzenkov wrote:
Do you really need multipath? Then you probably need to give more details about your configuration. It is rather unusual on consumer grade systems.
Actually, I neither need it, nor did I know what it was about before I saw this error message. Multipath is disabled in yast, and I have no idea what to do to avoid the error in dracut. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
28.09.2015 10:17, auxsvr@gmail.com пишет:
On Monday 28 of September 2015 09:26:35 Andrei Borzenkov wrote:
Do you really need multipath? Then you probably need to give more details about your configuration. It is rather unusual on consumer grade systems.
Actually, I neither need it, nor did I know what it was about before I saw this error message. Multipath is disabled in yast, and I have no idea what to do to avoid the error in dracut.
I do not remember that dracut included multipath in 13.2 and I do not see it in my test TW VM either. Running mkinitrd -vvvvvv to increase verbosity may give some hint. But normally unless it is used for root device it should not be included. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 28 of September 2015 19:51:18 Andrei Borzenkov wrote:
I do not remember that dracut included multipath in 13.2 and I do not see it in my test TW VM either. Running mkinitrd -vvvvvv to increase verbosity may give some hint. But normally unless it is used for root device it should not be included.
I disabled it (omit_dracutmodules+="multipath") and boot fails immediately. If I leave it in, then there is a >50% chance that boot fails after a delay, searching for the root device. Any ideas? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
02.10.2015 15:48, auxsvr пишет:
On Monday 28 of September 2015 19:51:18 Andrei Borzenkov wrote:
I do not remember that dracut included multipath in 13.2 and I do not see it in my test TW VM either. Running mkinitrd -vvvvvv to increase verbosity may give some hint. But normally unless it is used for root device it should not be included.
I disabled it (omit_dracutmodules+="multipath") and boot fails immediately. If I leave it in, then there is a >50% chance that boot fails after a delay, searching for the root device. Any ideas?
It sounds like for some reason multipath is used for your root. Not sure what information to ask ... probably running supportconfig to gather as much as possible. Look for supportutils on software.opensuse.org. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday 04 of October 2015 09:53:26 Andrei Borzenkov wrote:
It sounds like for some reason multipath is used for your root. Not sure what information to ask ... probably running supportconfig to gather as much as possible. Look for supportutils on software.opensuse.org.
When the system boots with multipath in dracut but disabled by systemd, # multipath -v2 # # multipath -ll ST31000528AS_9VP2VWC2 dm-2 ATA,ST31000528AS size=932G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 0:0:0:0 sda 8:0 active ready running WDC_WD800JB-00ETA0_WD-WMAHL1387773 dm-12 ATA,WDC WD800JB-00ET size=75G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 5:0:0:0 sdd 8:48 active ready running ST3120811AS_6PT0TQ9P dm-0 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 2:0:0:0 sdc 8:32 active ready running WDC_WD1200JD-00GBB0_WD-WMAES3432850 dm-1 ATA,WDC WD1200JD-00G size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 1:0:0:0 sdb 8:16 active ready running # /sbin/dmsetup table ST31000528AS_9VP2VWC2-part2: 0 921600000 linear 254:2 206848 ST31000528AS_9VP2VWC2-part1: 0 204800 linear 254:2 2048 ST31000528AS_9VP2VWC2: 0 1953525168 multipath 0 0 1 1 service-time 0 1 2 8:0 1 1 ST3120811AS_6PT0TQ9P-part2: 0 234018855 linear 254:0 417690 house-home: 0 108183552 linear 254:11 384 house-home: 108183552 111550464 linear 254:9 384 house-home: 219734016 122880000 linear 254:6 384 house-home: 342614016 152371200 linear 254:13 384 ST3120811AS_6PT0TQ9P-part1: 0 401625 linear 254:0 16065 WDC_WD800JB-00ETA0_WD-WMAHL1387773-part2: 0 3903795 linear 254:12 152392590 WDC_WD800JB-00ETA0_WD-WMAHL1387773: 0 156301488 multipath 0 0 1 1 service-time 0 1 2 8:48 1 1 WDC_WD800JB-00ETA0_WD-WMAHL1387773-part1: 0 152392527 linear 254:12 63 ST3120811AS_6PT0TQ9P: 0 234441648 multipath 0 0 1 1 service-time 0 1 2 8:32 1 1 ST31000528AS_9VP2VWC2-part6: 0 562896896 linear 254:2 1390626816 WDC_WD1200JD-00GBB0_WD-WMAES3432850: 0 234441648 multipath 0 0 1 1 service-time 0 1 2 8:16 1 1 house-system: 0 125829120 linear 254:11 108183936 ST31000528AS_9VP2VWC2-part5: 0 117184512 linear 254:2 1273440256 WDC_WD1200JD-00GBB0_WD-WMAES3432850-part2: 0 111555360 linear 254:1 122881185 ST31000528AS_9VP2VWC2-part4: 0 2 linear 254:2 921806848 WDC_WD1200JD-00GBB0_WD-WMAES3432850-part1: 0 122881122 linear 254:1 63 This means that multipath is not used on my system, if I'm reading it correctly. Then, why does dracut need it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
04.10.2015 14:32, auxsvr пишет:
On Sunday 04 of October 2015 09:53:26 Andrei Borzenkov wrote:
It sounds like for some reason multipath is used for your root. Not sure what information to ask ... probably running supportconfig to gather as much as possible. Look for supportutils on software.opensuse.org.
When the system boots with multipath in dracut but disabled by systemd,
# multipath -v2 #
# multipath -ll ST31000528AS_9VP2VWC2 dm-2 ATA,ST31000528AS size=932G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 0:0:0:0 sda 8:0 active ready running WDC_WD800JB-00ETA0_WD-WMAHL1387773 dm-12 ATA,WDC WD800JB-00ET size=75G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 5:0:0:0 sdd 8:48 active ready running ST3120811AS_6PT0TQ9P dm-0 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 2:0:0:0 sdc 8:32 active ready running WDC_WD1200JD-00GBB0_WD-WMAES3432850 dm-1 ATA,WDC WD1200JD-00G size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 1:0:0:0 sdb 8:16 active ready running
# /sbin/dmsetup table ST31000528AS_9VP2VWC2-part2: 0 921600000 linear 254:2 206848 ST31000528AS_9VP2VWC2-part1: 0 204800 linear 254:2 2048 ST31000528AS_9VP2VWC2: 0 1953525168 multipath 0 0 1 1 service-time 0 1 2 8:0 1 1 ST3120811AS_6PT0TQ9P-part2: 0 234018855 linear 254:0 417690 house-home: 0 108183552 linear 254:11 384 house-home: 108183552 111550464 linear 254:9 384 house-home: 219734016 122880000 linear 254:6 384 house-home: 342614016 152371200 linear 254:13 384 ST3120811AS_6PT0TQ9P-part1: 0 401625 linear 254:0 16065 WDC_WD800JB-00ETA0_WD-WMAHL1387773-part2: 0 3903795 linear 254:12 152392590 WDC_WD800JB-00ETA0_WD-WMAHL1387773: 0 156301488 multipath 0 0 1 1 service-time 0 1 2 8:48 1 1 WDC_WD800JB-00ETA0_WD-WMAHL1387773-part1: 0 152392527 linear 254:12 63 ST3120811AS_6PT0TQ9P: 0 234441648 multipath 0 0 1 1 service-time 0 1 2 8:32 1 1 ST31000528AS_9VP2VWC2-part6: 0 562896896 linear 254:2 1390626816 WDC_WD1200JD-00GBB0_WD-WMAES3432850: 0 234441648 multipath 0 0 1 1 service-time 0 1 2 8:16 1 1 house-system: 0 125829120 linear 254:11 108183936 ST31000528AS_9VP2VWC2-part5: 0 117184512 linear 254:2 1273440256 WDC_WD1200JD-00GBB0_WD-WMAES3432850-part2: 0 111555360 linear 254:1 122881185 ST31000528AS_9VP2VWC2-part4: 0 2 linear 254:2 921806848 WDC_WD1200JD-00GBB0_WD-WMAES3432850-part1: 0 122881122 linear 254:1 63
This means that multipath is not used on my system, if I'm reading it correctly.
This output does not include any indication of usage. Show at least /proc/mounts
Then, why does dracut need it?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday 04 of October 2015 20:19:47 Andrei Borzenkov wrote:
This output does not include any indication of usage. Show at least /proc/mounts
# cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 devtmpfs /dev devtmpfs rw,nosuid,size=2499836k,nr_inodes=624959,mode=755 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0 tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd- cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0 cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0 /dev/mapper/house-system / ext4 rw,relatime,data=ordered 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=29,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 /dev/mapper/ST3120811AS_6PT0TQ9P-part1 /boot ext3 rw,relatime,data=ordered 0 0 /dev/mapper/house-home /home ext4 rw,nosuid,nodev,relatime,data=ordered 0 0 /dev/mapper/ST31000528AS_9VP2VWC2-part2 /home/petros/mnt btrfs rw,nosuid,nodev,noexec,relatime,space_cache 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 none /var/lib/ntp/proc proc ro,nosuid,nodev,relatime 0 0 gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
04.10.2015 20:30, auxsvr пишет:
On Sunday 04 of October 2015 20:19:47 Andrei Borzenkov wrote:
This output does not include any indication of usage. Show at least /proc/mounts
# cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 devtmpfs /dev devtmpfs rw,nosuid,size=2499836k,nr_inodes=624959,mode=755 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0 tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd- cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0 cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0 /dev/mapper/house-system / ext4 rw,relatime,data=ordered 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=29,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 /dev/mapper/ST3120811AS_6PT0TQ9P-part1 /boot ext3 rw,relatime,data=ordered 0 0 /dev/mapper/house-home /home ext4 rw,nosuid,nodev,relatime,data=ordered 0 0 /dev/mapper/ST31000528AS_9VP2VWC2-part2 /home/petros/mnt btrfs rw,nosuid,nodev,noexec,relatime,space_cache 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 none /var/lib/ntp/proc proc ro,nosuid,nodev,relatime 0 0 gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0
Could you show "dmsetup ls" to display minor numbers as well? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 05 of October 2015 06:26:58 Andrei Borzenkov wrote:
04.10.2015 20:30, auxsvr пишет:
On Sunday 04 of October 2015 20:19:47 Andrei Borzenkov wrote:
This output does not include any indication of usage. Show at least /proc/mounts
# cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 devtmpfs /dev devtmpfs rw,nosuid,size=2499836k,nr_inodes=624959,mode=755 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0 tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd /systemd- cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0 cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0 /dev/mapper/house-system / ext4 rw,relatime,data=ordered 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=29,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 /dev/mapper/ST3120811AS_6PT0TQ9P-part1 /boot ext3 rw,relatime,data=ordered 0 0 /dev/mapper/house-home /home ext4 rw,nosuid,nodev,relatime,data=ordered 0 0 /dev/mapper/ST31000528AS_9VP2VWC2-part2 /home/petros/mnt btrfs rw,nosuid,nodev,noexec,relatime,space_cache 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 none /var/lib/ntp/proc proc ro,nosuid,nodev,relatime 0 0 gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0
Could you show "dmsetup ls" to display minor numbers as well?
Sure, # dmsetup ls ST31000528AS_9VP2VWC2-part2 (254:4) ST31000528AS_9VP2VWC2-part1 (254:3) ST31000528AS_9VP2VWC2 (254:0) ST3120811AS_6PT0TQ9P-part2 (254:12) house-home (254:16) ST3120811AS_6PT0TQ9P-part1 (254:11) WDC_WD800JB-00ETA0_WD-WMAHL1387773-part2 (254:14) WDC_WD800JB-00ETA0_WD-WMAHL1387773 (254:10) WDC_WD800JB-00ETA0_WD-WMAHL1387773-part1 (254:13) ST3120811AS_6PT0TQ9P (254:2) ST31000528AS_9VP2VWC2-part6 (254:7) WDC_WD1200JD-00GBB0_WD-WMAES3432850 (254:1) house-system (254:15) ST31000528AS_9VP2VWC2-part5 (254:6) WDC_WD1200JD-00GBB0_WD-WMAES3432850-part2 (254:9) ST31000528AS_9VP2VWC2-part4 (254:5) WDC_WD1200JD-00GBB0_WD-WMAES3432850-part1 (254:8) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Oct 4, 2015 at 2:32 PM, auxsvr <auxsvr@gmail.com> wrote:
# multipath -ll ST31000528AS_9VP2VWC2 dm-2 ATA,ST31000528AS size=932G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 0:0:0:0 sda 8:0 active ready running
...
# /sbin/dmsetup table ST31000528AS_9VP2VWC2-part2: 0 921600000 linear 254:2 206848 ST31000528AS_9VP2VWC2-part1: 0 204800 linear 254:2 2048 ST31000528AS_9VP2VWC2: 0 1953525168 multipath 0 0 1 1 service-time 0 1 2 8:0 1 1
...
house-system: 0 125829120 linear 254:11 108183936 ... /dev/mapper/house-system / ext4 rw,relatime,data=ordered 0 0 ... # dmsetup ls ST3120811AS_6PT0TQ9P-part1 (254:11) ST3120811AS_6PT0TQ9P (254:2)
So your root is /dev/mapper/house-system which itself sits on top of device 254:11 which is ST3120811AS_6PT0TQ9P-part1 which sits on top of ST31000528AS_9VP2VWC2 which *is* multpath device. In retrospect "dmsetup ls --tree" had made it easier probably :) So you do use multipath for your root. I have no idea why. Could you please show /etc/multipath.conf (probably as "grep -v '^#' to strip off comments). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 05 of October 2015 09:46:38 Andrei Borzenkov wrote:
On Sun, Oct 4, 2015 at 2:32 PM, auxsvr <auxsvr@gmail.com> wrote:
# dmsetup ls ST3120811AS_6PT0TQ9P-part1 (254:11) ST3120811AS_6PT0TQ9P (254:2)
So your root is /dev/mapper/house-system which itself sits on top of device 254:11 which is ST3120811AS_6PT0TQ9P-part1 which sits on top of ST31000528AS_9VP2VWC2 which *is* multpath device. In retrospect "dmsetup ls --tree" had made it easier probably :)
So you do use multipath for your root. I have no idea why. Could you please show /etc/multipath.conf (probably as "grep -v '^#' to strip off comments).
I don't think so, # dmsetup ls --tree ST31000528AS_9VP2VWC2-part2 (254:4) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0) ST31000528AS_9VP2VWC2-part1 (254:3) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0) house-home (254:16) ├─WDC_WD800JB-00ETA0_WD-WMAHL1387773-part1 (254:13) │ └─WDC_WD800JB-00ETA0_WD-WMAHL1387773 (254:10) │ └─ (8:48) ├─WDC_WD1200JD-00GBB0_WD-WMAES3432850-part1 (254:8) │ └─WDC_WD1200JD-00GBB0_WD-WMAES3432850 (254:1) │ └─ (8:16) ├─WDC_WD1200JD-00GBB0_WD-WMAES3432850-part2 (254:9) │ └─WDC_WD1200JD-00GBB0_WD-WMAES3432850 (254:1) │ └─ (8:16) └─ST3120811AS_6PT0TQ9P-part2 (254:12) └─ST3120811AS_6PT0TQ9P (254:2) └─ (8:32) ST3120811AS_6PT0TQ9P-part1 (254:11) └─ST3120811AS_6PT0TQ9P (254:2) └─ (8:32) WDC_WD800JB-00ETA0_WD-WMAHL1387773-part2 (254:14) └─WDC_WD800JB-00ETA0_WD-WMAHL1387773 (254:10) └─ (8:48) ST31000528AS_9VP2VWC2-part6 (254:7) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0) house-system (254:15) └─ST3120811AS_6PT0TQ9P-part2 (254:12) └─ST3120811AS_6PT0TQ9P (254:2) └─ (8:32) ST31000528AS_9VP2VWC2-part5 (254:6) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0) ST31000528AS_9VP2VWC2-part4 (254:5) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0) My root sits on 254:12, which is independent of ST31000528AS_9VP2VWC2; the latter is a disk with a btrfs partition mounted on /home/petros/mnt. dmsetup table still indicates that no device is multipath-enabled (I'm reading the numbers after the word multipath and they're <=1), also multipathd is not running. The weird thing is that a file /etc/multipath/wwids now exists, which didn't exist yesterday. Its contents are: # Valid WWIDs: /ST31000528AS_9VP2VWC2/ /WDC_WD1200JD-00GBB0_WD-WMAES3432850/ /ST3120811AS_6PT0TQ9P/ /WDC_WD800JB-00ETA0_WD-WMAHL1387773/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Oct 5, 2015 at 10:16 AM, auxsvr <auxsvr@gmail.com> wrote:
On Monday 05 of October 2015 09:46:38 Andrei Borzenkov wrote:
On Sun, Oct 4, 2015 at 2:32 PM, auxsvr <auxsvr@gmail.com> wrote:
# dmsetup ls ST3120811AS_6PT0TQ9P-part1 (254:11) ST3120811AS_6PT0TQ9P (254:2)
So your root is /dev/mapper/house-system which itself sits on top of device 254:11 which is ST3120811AS_6PT0TQ9P-part1 which sits on top of ST31000528AS_9VP2VWC2 which *is* multpath device. In retrospect "dmsetup ls --tree" had made it easier probably :)
So you do use multipath for your root. I have no idea why. Could you please show /etc/multipath.conf (probably as "grep -v '^#' to strip off comments).
I don't think so,
# dmsetup ls --tree ST31000528AS_9VP2VWC2-part2 (254:4) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0) ST31000528AS_9VP2VWC2-part1 (254:3) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0) house-home (254:16) ├─WDC_WD800JB-00ETA0_WD-WMAHL1387773-part1 (254:13) │ └─WDC_WD800JB-00ETA0_WD-WMAHL1387773 (254:10) │ └─ (8:48) ├─WDC_WD1200JD-00GBB0_WD-WMAES3432850-part1 (254:8) │ └─WDC_WD1200JD-00GBB0_WD-WMAES3432850 (254:1) │ └─ (8:16) ├─WDC_WD1200JD-00GBB0_WD-WMAES3432850-part2 (254:9) │ └─WDC_WD1200JD-00GBB0_WD-WMAES3432850 (254:1) │ └─ (8:16) └─ST3120811AS_6PT0TQ9P-part2 (254:12) └─ST3120811AS_6PT0TQ9P (254:2) └─ (8:32) ST3120811AS_6PT0TQ9P-part1 (254:11) └─ST3120811AS_6PT0TQ9P (254:2) └─ (8:32) WDC_WD800JB-00ETA0_WD-WMAHL1387773-part2 (254:14) └─WDC_WD800JB-00ETA0_WD-WMAHL1387773 (254:10) └─ (8:48) ST31000528AS_9VP2VWC2-part6 (254:7) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0) house-system (254:15) └─ST3120811AS_6PT0TQ9P-part2 (254:12) └─ST3120811AS_6PT0TQ9P (254:2) └─ (8:32)
This is multipath device. ST3120811AS_6PT0TQ9P dm-0 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 2:0:0:0 sdc 8:32 active ready running
ST31000528AS_9VP2VWC2-part5 (254:6) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0) ST31000528AS_9VP2VWC2-part4 (254:5) └─ST31000528AS_9VP2VWC2 (254:0) └─ (8:0)
My root sits on 254:12, which is independent of ST31000528AS_9VP2VWC2; the latter is a disk with a btrfs partition mounted on /home/petros/mnt. dmsetup table still indicates that no device is multipath-enabled (I'm reading the numbers after the word multipath and they're <=1), also multipathd is not running. The weird thing is that a file /etc/multipath/wwids now exists, which didn't exist yesterday. Its contents are:
# Valid WWIDs: /ST31000528AS_9VP2VWC2/ /WDC_WD1200JD-00GBB0_WD-WMAES3432850/ /ST3120811AS_6PT0TQ9P/ /WDC_WD800JB-00ETA0_WD-WMAHL1387773/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 05 of October 2015 10:29:50 Andrei Borzenkov wrote:
This is multipath device.
ST3120811AS_6PT0TQ9P dm-0 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 2:0:0:0 sdc 8:32 active ready running
This changed since yesterday, ST3120811AS_6PT0TQ9P dm-2 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 2:0:0:0 sdc 8:32 active ready running I don't know much about this, but, according to the documentation, dmsetup table indicates the number of paths, which should be >1 for a multipath device. Also, during boot, before the root is mounted, multipathd[734]: ok multipathd[288]: path checkers start up multipathd[288]: sda: failed to get uid: Invalid argument multipathd[288]: sda: failed to get uid: Invalid argument multipathd[288]: sdb: failed to get uid: Invalid argument multipathd[288]: sdb: failed to get uid: Invalid argument multipathd[288]: sdc: failed to get uid: Invalid argument multipathd[288]: sdc: failed to get uid: Invalid argument multipathd[288]: sda: add path (uevent) multipathd[288]: sda: spurious uevent, path already in pathvec multipathd[288]: ST31000528AS_9VP2VWC2: load table [0 1953525168 multipath 0 0 1 1 service-time 0 1 1 8:0 1] multipathd[288]: ST31000528AS_9VP2VWC2: event checker started multipathd[288]: sda [8:0]: path added to devmap ST31000528AS_9VP2VWC2 multipathd[288]: sdb: add path (uevent) multipathd[288]: sdb: spurious uevent, path already in pathvec multipathd[288]: WDC_WD1200JD-00GBB0_WD-WMAES3432850: load table [0 234441648 multipath 0 0 1 1 service-time 0 1 1 8:16 1] multipathd[288]: WDC_WD1200JD-00GBB0_WD-WMAES3432850: event checker started multipathd[288]: sdb [8:16]: path added to devmap WDC_WD1200JD-00GBB0_WD-WMAES3432850 multipathd[288]: sdc: add path (uevent) multipathd[288]: sdc: spurious uevent, path already in pathvec multipathd[288]: ST3120811AS_6PT0TQ9P: load table [0 234441648 multipath 0 0 1 1 service-time 0 1 1 8:32 1] multipathd[288]: ST3120811AS_6PT0TQ9P: event checker started multipathd[288]: sdc [8:32]: path added to devmap ST3120811AS_6PT0TQ9P multipathd[288]: sdd: add path (uevent) multipathd[288]: WDC_WD800JB-00ETA0_WD-WMAHL1387773: load table [0 156301488 multipath 0 0 1 1 service-time 0 1 1 8:48 1] multipathd[288]: WDC_WD800JB-00ETA0_WD-WMAHL1387773: event checker started multipathd[288]: sdd [8:48]: path added to devmap WDC_WD800JB-00ETA0_WD- WMAHL1387773 multipathd[288]: ST31000528AS_9VP2VWC2: stop event checker thread (140410342287104) multipathd[288]: WDC_WD1200JD-00GBB0_WD-WMAES3432850: stop event checker thread (140410342250240) multipathd[288]: ST3120811AS_6PT0TQ9P: stop event checker thread (140410342213376) multipathd[288]: WDC_WD800JB-00ETA0_WD-WMAHL1387773: stop event checker thread (140410342176512) multipathd[288]: --------shut down------- There is no reason for multipath on this system, unless systemd or dracut do something weird. Perhaps this is related to the fact that I've been using these disks for several years with different motherboards, originally with a RAID controller that wrote some metadata on them (they were appearing as RAID disks in lsblk -f, even though I've never used any RAID feature). The booting problem started after the transition to dracut, and shortly thereafter I removed the metadata. Perhaps some of it is still left? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Oct 5, 2015 at 11:05 AM, auxsvr <auxsvr@gmail.com> wrote:
On Monday 05 of October 2015 10:29:50 Andrei Borzenkov wrote:
This is multipath device.
ST3120811AS_6PT0TQ9P dm-0 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 2:0:0:0 sdc 8:32 active ready running
This changed since yesterday,
In which way exactly?
ST3120811AS_6PT0TQ9P dm-2 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 2:0:0:0 sdc 8:32 active ready running
I don't know much about this, but, according to the documentation, dmsetup table indicates the number of paths, which should be >1 for a multipath device.
??? Number of paths is determined by physical connectivity. ...
There is no reason for multipath on this system, unless systemd or dracut do something weird.
Sure, systemd is the source of all evil, what else ... so change /etc/fstab to use device-independent mounts (like LABEL or UUID), reboot to verify, disable multipathd.service and multipathd.socket, disable multipath dracut module, recreate initrd and test again. It make sense to rename original initrd before so you have something to manually fall back to. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 05 of October 2015 11:14:20 Andrei Borzenkov wrote:
On Mon, Oct 5, 2015 at 11:05 AM, auxsvr <auxsvr@gmail.com> wrote:
On Monday 05 of October 2015 10:29:50 Andrei Borzenkov wrote:
This is multipath device.
ST3120811AS_6PT0TQ9P dm-0 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active
`- 2:0:0:0 sdc 8:32 active ready running
This changed since yesterday,
In which way exactly?
dm-0 turned to dm-2. Perhaps I'm missing something obvious; which part of this output indicates that the device is multipathed?
I don't know much about this, but, according to the documentation, dmsetup table indicates the number of paths, which should be >1 for a multipath device.
??? Number of paths is determined by physical connectivity.
Doesn't this imply that no device is multipathed in my case?
There is no reason for multipath on this system, unless systemd or dracut do something weird.
Sure, systemd is the source of all evil, what else ... so change /etc/fstab to use device-independent mounts (like LABEL or UUID), reboot to verify, disable multipathd.service and multipathd.socket, disable multipath dracut module, recreate initrd and test again. It make sense to rename original initrd before so you have something to manually fall back to.
Actually, I quite like systemd, but I've been bitten by its bugs many times (there's still a bug with logind after restarting dbus that delays logins and spams the system log). multipathd.{service,socket} are disabled, I'll try the rest after some hours, because I need the system at the moment. Also, this[1] and this[2] may be relevant. -------- [1] http://lists.freedesktop.org/archives/systemd-devel/2014-October/024591.html [2] http://www.spinics.net/lists/dm-devel/msg22309.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Oct 5, 2015 at 11:48 AM, auxsvr <auxsvr@gmail.com> wrote:
On Monday 05 of October 2015 11:14:20 Andrei Borzenkov wrote:
On Mon, Oct 5, 2015 at 11:05 AM, auxsvr <auxsvr@gmail.com> wrote:
On Monday 05 of October 2015 10:29:50 Andrei Borzenkov wrote:
This is multipath device.
ST3120811AS_6PT0TQ9P dm-0 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active
`- 2:0:0:0 sdc 8:32 active ready running
This changed since yesterday,
In which way exactly?
dm-0 turned to dm-2.
it does not matter. Device names are not and never were stable and can change between reboots or even during system uptime (if you remove and then add back the same device).
Perhaps I'm missing something obvious; which part of this output indicates that the device is multipathed?
The very fact that it is output of "multipath -l" command :)
I don't know much about this, but, according to the documentation, dmsetup table indicates the number of paths, which should be >1 for a multipath device.
??? Number of paths is determined by physical connectivity.
Doesn't this imply that no device is multipathed in my case?
Do not attempt to interpret names. We are speaking about driver that is called "multipath". While its purpose is indeed to work with multiple paths to a single device, this is by no means necessary for the driver to work.
There is no reason for multipath on this system, unless systemd or dracut do something weird.
Sure, systemd is the source of all evil, what else ... so change /etc/fstab to use device-independent mounts (like LABEL or UUID), reboot to verify, disable multipathd.service and multipathd.socket, disable multipath dracut module, recreate initrd and test again. It make sense to rename original initrd before so you have something to manually fall back to.
Actually, I quite like systemd, but I've been bitten by its bugs many times (there's still a bug with logind after restarting dbus that delays logins and spams the system log). multipathd.{service,socket} are disabled,
It is not clear - did you disable them now or they were disabled all the time? Do the run now (systemctl status multipathd.{service,socket})? Remember, "disabled" does not mean "cannot start".
I'll try the rest after some hours, because I need the system at the moment. Also, this[1] and this[2] may be relevant.
-------- [1] http://lists.freedesktop.org/archives/systemd-devel/2014-October/024591.html
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
After upgrading to oS Leap, dracut boots the system normally. Apparently, the problem was due to the race between multipath and udev, but I still have no idea why my system requires multipath in the first place! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrei Borzenkov -
auxsvr -
auxsvr＠gmail.com