[Bug 1207387] New: mdam : monitoring detected DeviceDisappeared
http://bugzilla.opensuse.org/show_bug.cgi?id=1207387 Bug ID: 1207387 Summary: mdam : monitoring detected DeviceDisappeared Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: holgerbruenjes@gmx.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hello it ist the package mdadm-4.2-5.1.src.rpm from tumbleweed I use the mdadm tool also in the past my mdadm.conf cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md1 UUID=6c9f3d38:ada07516:3d186b3c:53958f34 ARRAY /dev/md/2 metadata=1.2 UUID=6bb43ca5:fab488e0:590a1132:6d893542 name=(none):2 ARRAY /dev/md/3 metadata=1.2 UUID=af96a8a7:8355bc0e:7e877926:835dd720 name=(none):3 PROGRAM /usr/libexec/mdadm/mdadm-event-handler.sh eis-5351:/ # eis-5351:/ # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] md3 : active raid1 sdb3[0] sda3[1] 312198464 blocks super 1.2 [2/2] [UU] bitmap: 2/3 pages [8KB], 65536KB chunk md2 : active raid1 sdb2[0] sda2[1] 130048 blocks super 1.2 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk md1 : active raid1 sdb1[0] sda1[1] 98240 blocks [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk unused devices: <none> eis-5351:/ # ll /dev/md* brw-rw---- 1 root disk 9, 1 2023-01-23 09:38 /dev/md1 brw-rw---- 1 root disk 9, 2 2023-01-23 09:38 /dev/md2 brw-rw---- 1 root disk 9, 3 2023-01-23 09:38 /dev/md3 /dev/md: total 0 lrwxrwxrwx 1 root root 6 2023-01-23 09:38 2 -> ../md2 lrwxrwxrwx 1 root root 6 2023-01-23 09:38 3 -> ../md3 eis-5351:/ # blkid /dev/sda1: UUID="6c9f3d38-ada0-7516-3d18-6b3c53958f34" TYPE="linux_raid_member" PARTLABEL="boot" PARTUUID="30c4a077-5317-452e-9790-38907f0e2c23" /dev/sda2: UUID="6bb43ca5-fab4-88e0-590a-11326d893542" UUID_SUB="433c3917-8a67-201f-9cc6-488bc3cd40e5" LABEL="(none):2" TYPE="linux_raid_member" PARTLABEL="swap" PARTUUID="e29917a8-1adb-468d-bd89-45881e64e68f" /dev/sda3: UUID="af96a8a7-8355-bc0e-7e87-7926835dd720" UUID_SUB="d92de6c9-7df5-007a-cf88-4cbb7ca9a315" LABEL="(none):3" TYPE="linux_raid_member" PARTLABEL="root" PARTUUID="6bc85123-3938-4e6e-b8b2-1fa47786b66a" /dev/sdb1: UUID="6c9f3d38-ada0-7516-3d18-6b3c53958f34" TYPE="linux_raid_member" PARTLABEL="boot" PARTUUID="5c3f7a62-f9ad-4500-9ef3-3f736249b0e5" /dev/sdb2: UUID="6bb43ca5-fab4-88e0-590a-11326d893542" UUID_SUB="0b6cc352-863b-e379-5808-43b9e578c451" LABEL="(none):2" TYPE="linux_raid_member" PARTLABEL="swap" PARTUUID="9d942155-db32-4e57-ad42-4b331c76ac06" /dev/sdb3: UUID="af96a8a7-8355-bc0e-7e87-7926835dd720" UUID_SUB="bd272b7c-b5b6-efea-9375-e5d830899a38" LABEL="(none):3" TYPE="linux_raid_member" PARTLABEL="root" PARTUUID="3f876df5-8321-4e80-8de2-fd9101e1e620" /dev/md1: UUID="30b5bb75-d24e-4da1-ac44-982964ce4249" BLOCK_SIZE="1024" TYPE="ext4" /dev/md2: UUID="9b09c4e7-14ea-4800-a4b2-8074b59c8de2" TYPE="swap" /dev/md3: UUID="efd4a549-d390-4146-9125-546edd68cf60" BLOCK_SIZE="4096" TYPE="ext4" I use this test cmd mdadm --monitor --oneshot --scan --test and now it triggered 6 mail ------------------- Dispatched from mdadm Agent on Server 'eis-5351' Current Date: 2023-01-21 Time: 21:40:45 Host : eis-5351 MD Device : /dev/md/3 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md/2 Event : TestMessage ... this device never existed and it cannot have disappeared as a result. Host : eis-5351 MD Device : /dev/md/md1 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md/md1 Event : DeviceDisappeared ... Host : eis-5351 MD Device : /dev/md1 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md1 Event : NewArray -------------------------- and after boot it triggerd 1 mail Host : eis-5351 MD Device : /dev/md1 Event : NewArray -------------------- in the past with mdadm 4.1-13.2 it triggered 3 mail --------------- Dispatched from mdadm Agent on Server 'eis-5351' Current Date: 2023-01-21 Time: 16:38:13 Host : eis-5351 MD Device : /dev/md/3 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md/2 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md1 Event : TestMessage ---------------------------------- it this now a feature or a bug I detected his patch for the problem 0029-Monitor-use-snprintf-to-fill-device-name.patch it contained your vote Signed-off-by: Coly Li <colyli@suse.de> and drop adding this patch, as a result the patches 0046 and 0051 cannot be added, but i can't tell if the patches were just a consequence problem Thanks Holger -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207387 http://bugzilla.opensuse.org/show_bug.cgi?id=1207387#c1 Holger Bruenjes <holgerbruenjes@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Holger Bruenjes <holgerbruenjes@gmx.net> --- the difference is in the mdadm.conf and how it was created. mdadm --examine --scan is not good enough mdadm --detail --scan it must be with mdadm version 4.2 and greater Thanks to Kinga Tanska for the help Holger -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com