[Bug 887821] New: mdadm -Q --detail for RAID 1 segfaults
https://bugzilla.novell.com/show_bug.cgi?id=887821 https://bugzilla.novell.com/show_bug.cgi?id=887821#c0 Summary: mdadm -Q --detail for RAID 1 segfaults Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Willy.Weisz@univie.ac.at QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 mdadm -QE /dev/sdb3 gives: /dev/sdb3: Magic : a92b4efc Version : 1.0 Feature Map : 0x1 Array UUID : f27c6f43:4565068d:8febeadb:89a7a594 Name : linux:0 Creation Time : Sat Jan 22 22:18:24 2011 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 2576985840 (1228.80 GiB 1319.42 GB) Array Size : 1288492920 (1228.80 GiB 1319.42 GB) Super Offset : 2576986096 sectors Unused Space : before=0 sectors, after=96 sectors State : clean Device UUID : d5dc9ef7:a5c350c6:6cf7b7e4:dcbf390b Internal Bitmap : -160 sectors from superblock Update Time : Thu Jul 17 21:05:25 2014 Checksum : 7ac46ac6 - correct Events : 13505 Device Role : Active device 0 Array State : AA ('A' == active, '.' == missing, 'R' == replacing) The same goes for /dev/sdc3 the second partner in the RAID1. mdadm -Q /dev/dm-2 (the RAID1 device) produces: /dev/dm-2: 1173.80GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail. mdadm -Q --detail /dev/dm-2 produces /dev/dm-2: Version : 1.0 Creation Time : Sat Jan 22 22:18:24 2011 Raid Level : raid1 Array Size : 1230819328 (1173.80 GiB 1260.36 GB) Used Dev Size : unknown Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Thu Jul 17 21:44:53 2014 Segmentation fault Looking at dmesg I found 12 messages of the form: mdadm[29382]: segfault at 40 ip 000000000041d838 sp 00007fff40a21cc0 error 4 in mdadm[400000+76000] which differed in the process number and the value after "sp". Reproducible: Always Steps to Reproduce: 1. mdadm -Q --detail /dev/dm-2 (dm-2 being a RAID1 device) 2. 3. Actual Results: Segmentation fault Expected Results: Listing of RAID1 details -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887821 https://bugzilla.novell.com/show_bug.cgi?id=887821#c1 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |nfbrown@suse.com InfoProvider| |Willy.Weisz@univie.ac.at AssignedTo|bnc-team-screening@forge.pr |nfbrown@suse.com |ovo.novell.com | --- Comment #1 from Neil Brown <nfbrown@suse.com> 2014-07-24 07:54:36 UTC --- mdadm certainly shouldn't segfault, however .... /dev/dm-2 is an unusual name for an md device. /dev/md2 is more likely. Is the array managed by mdadm or lvm2 or dmraid or something else??? What does cat /proc/mdstat dmsetup table ls -l /dev/dm-2 show?? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887821 https://bugzilla.novell.com/show_bug.cgi?id=887821#c2 Willy Weisz <Willy.Weisz@univie.ac.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |Willy.Weisz@univie.ac.at InfoProvider|Willy.Weisz@univie.ac.at | --- Comment #2 from Willy Weisz <Willy.Weisz@univie.ac.at> 2014-07-24 10:28:00 UTC --- It took me quite some experimentation to find out the device name of the RAID1 array. It is /dev/dm-2; there is no /dev/md*. The array was created as RAID1 by the openSuSE installation processes and afterwards an lvm2 volume group was installed on it. The information you requested is: # cat /proc/mdstat Personalities : [linear] [raid1] md127 : active raid1 sdb3[0] sdc3[1] 1288492920 blocks super 1.0 [2/2] [UU] bitmap: 0/308 pages [0KB], 2048KB chunk unused devices: <none> # dmsetup table vg00-home: 0 2461638656 linear 9:127 384 vg00-usr: 0 83886080 linear 9:127 2482610560 vg00-var: 0 10485760 linear 9:127 2566496640 opensuse-linux--root: 0 377479168 linear 8:3 2048 vg00-root: 0 20971520 linear 9:127 2461639040 opensuse-linux--var: 0 41943040 linear 8:3 377481216 # ls -l /dev/dm-2 brw-rw---- 1 root disk 253, 2 Jul 19 22:04 /dev/dm-2 I hope this helps solving the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887821 https://bugzilla.novell.com/show_bug.cgi?id=887821#c3 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |Willy.Weisz@univie.ac.at --- Comment #3 from Neil Brown <nfbrown@suse.com> 2014-07-24 10:47:27 UTC --- /dev/dm-2 is one of the LVM2 volumes that makes use of the RAID1 array. "mdadm -D" on that should report that it isn't an md device, I cannot imagine why it would be behaving as it does. I'll look into that next week. Also there really should be a "/dev/md127" - udev will create that. Is there nothing in /dev/md/ either? If you run udevadm trigger does /dev/md127 appear? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887821 https://bugzilla.novell.com/show_bug.cgi?id=887821#c4 --- Comment #4 from Willy Weisz <Willy.Weisz@univie.ac.at> 2014-07-24 11:06:54 UTC --- You're right: the RAID1 device is /dev/md127, and mdadm gives the detail information expected when run against it. So this bug report may be closed. Nevertheless just segfaulting isn't a very informative answer to tell the user he made the request on a wrong device. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887821 https://bugzilla.novell.com/show_bug.cgi?id=887821#c5 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|Willy.Weisz@univie.ac.at | Resolution| |FIXED --- Comment #5 from Neil Brown <nfbrown@suse.com> 2014-08-06 06:00:54 UTC --- I've fixed this problem in the upstream mdadm. So the fix will be in mdadm 3.3.2 and probably in openSUSE:13.2. I don't think it particularly needs a openSUSE:13.1 update. Thanks for the report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com