Bug#963239: Info received (Bug #963239 linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5))
Resync triggered again (September 23) for no apparent reason : sudo dmesg | grep md127 [3.042521] md/raid:md127: not clean -- starting background reconstruction [3.042531] md/raid:md127: device sda1 operational as raid disk 0 [3.042531] md/raid:md127: device sdb1 operational as raid disk 1 [3.042531] md/raid:md127: device sdc1 operational as raid disk 2 [3.042741] md/raid:md127: raid level 5 active with 3 out of 3 devices, algorithm 2 [3.042811] md127: bitmap file is out of date (13477 < 13478) -- forcing full recovery [3.042820] md127: bitmap file is out of date, doing full recovery [3.128357] md127: detected capacity change from 0 to 1717716385792 [3.133982] md127: AHDI p1 p3 [3.134008] md127: p1 size 3214817840 extends beyond EOD, truncated [ 10.754470] md127: AHDI p1 p3 [ 10.754475] md127: p1 size 3214817840 extends beyond EOD, truncated [ 10.971872] md: resync of RAID array md127 cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] md127 : active raid5 sda1[0] sdb1[1] sdc1[3] 1677457408 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU] [==>..] resync = 10.9% (91796180/838728704) finish=77.8min speed=159943K/sec bitmap: 7/7 pages [28KB], 65536KB chunk unused devices: Eric
Bug#963239: Bug #963239 linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5)
The issue happened again. I noticed there could be a link with the fact that the computer is up for days and then at next reboot it triggers a reconstruction. (the 3 disks composing the raid device are healthy) The computer is very slow during reconstruction. sudo dmesg | grep md127: [ 18.394466] md/raid:md127: not clean -- starting background reconstruction [ 18.394475] md/raid:md127: device sdb1 operational as raid disk 1 [ 18.394476] md/raid:md127: device sdc1 operational as raid disk 2 [ 18.394476] md/raid:md127: device sda1 operational as raid disk 0 [ 18.394697] md/raid:md127: raid level 5 active with 3 out of 3 devices, algorithm 2 [ 18.394765] md127: bitmap file is out of date (10910 < 10911) -- forcing full recovery [ 18.394772] md127: bitmap file is out of date, doing full recovery [ 18.479938] md127: detected capacity change from 0 to 1717716385792 [ 18.485209] md127: AHDI p1 p3 [ 18.485234] md127: p1 size 3214817840 extends beyond EOD, truncated [ 29.228966] md127: AHDI p1 p3 [ 29.228970] md127: p1 size 3214817840 extends beyond EOD, truncated [ 29.554661] md: resync of RAID array md127 cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] md127 : active raid5 sdb1[1] sdc1[3] sda1[0] 1677457408 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU] [>] resync = 80.0% (671298352/838728704) finish=22.9min speed=121385K/sec bitmap: 7/7 pages [28KB], 65536KB chunk Eric
Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5)
Since some days, I noticed that "resync" of md device triggers at boot time. Sometimes, it triggers at every boot. It slows down the computer and the disks access for 90minutes. I didn't notice this kind of behavior at the beginning. Lately I didn't change anything except changing a component (PCI sound card) and keeping the OS up to date by installing the last updates. So I checked the health of the disks (with smartctl) and manually triggered a check of the array (with /usr/share/mdadm/checkarray). But everything looks good. In the log (first post) there are messages about the bitmap of the array and that is not clean forcing a reconstruction of the array. I don't think it's normal. Le dim. 21 juin 2020 à 22:53, Ben Hutchings a écrit : > Control: tag -1 moreinfo > > You need to explain what the bug is. The subject says that a RAID > array was resynced at boot, but that's supposed to happen in some > circumstances. > > * Why did you not expect it? > * Did you notice anything happen before, or did you make any change, > that might have triggered this behaviour? > * Does this happen repeatedly? > * If so, haved you tried anything to work around this, and did it > work? > > Ben. > > -- > Ben Hutchings > It is impossible to make anything foolproof > because fools are so ingenious. > > >
Processed: Re: Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5)
Processing control commands: > tag -1 moreinfo Bug #963239 [src:linux] linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5) Added tag(s) moreinfo. -- 963239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5)
Control: tag -1 moreinfo You need to explain what the bug is. The subject says that a RAID array was resynced at boot, but that's supposed to happen in some circumstances. * Why did you not expect it? * Did you notice anything happen before, or did you make any change, that might have triggered this behaviour? * Does this happen repeatedly? * If so, haved you tried anything to work around this, and did it work? Ben. -- Ben Hutchings It is impossible to make anything foolproof because fools are so ingenious. signature.asc Description: This is a digitally signed message part
Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5)
Package: src:linux Version: 4.19.118-2+deb10u1 Severity: normal -- Package-specific info: ** Version: Linux version 4.19.0-9-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-amd64 root=UUID=0fd77287-e4d7-4b55-8510-7f05a983267e ro quiet ipv6.disable=1 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [3.936969] mei_me :00:16.0: enabling device ( -> 0002) [3.975895] iTCO_vendor_support: vendor-support=0 [3.977469] EFI Variables Facility v0.08 2004-May-17 [3.977545] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [3.977651] iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400) [3.979240] usb 1-8.6: New USB device found, idVendor=0b95, idProduct=6801, bcdDevice= 0.02 [3.979241] usb 1-8.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.979242] usb 1-8.6: Product: AX68002 [3.979242] usb 1-8.6: Manufacturer: ASIX Electronics [3.979243] usb 1-8.6: SerialNumber: 0002 [3.984037] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [3.985350] input: ASIX Electronics AX68002 as /devices/pci:00/:00:14.0/usb1/1-8/1-8.6/1-8.6:1.0/0003:0B95:6801.0007/input/input7 [4.013873] input: PC Speaker as /devices/platform/pcspkr/input/input8 [4.014790] sd 2:0:0:0: Attached scsi generic sg0 type 0 [4.014809] sd 3:0:0:0: Attached scsi generic sg1 type 0 [4.014823] sr 4:0:0:0: Attached scsi generic sg2 type 5 [4.014837] sd 5:0:0:0: Attached scsi generic sg3 type 0 [4.018291] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.018414] snd_hda_intel :01:00.1: enabling device ( -> 0002) [4.018458] snd_hda_intel :01:00.1: Disabling MSI [4.018461] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [4.018732] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer [4.018732] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules [4.018733] RAPL PMU: hw unit of domain package 2^-14 Joules [4.018733] RAPL PMU: hw unit of domain dram 2^-14 Joules [4.018733] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules [4.018733] RAPL PMU: hw unit of domain psys 2^-14 Joules [4.044941] hid-generic 0003:0B95:6801.0007: input,hidraw3: USB HID v1.10 Keyboard [ASIX Electronics AX68002] on usb-:00:14.0-8.6/input0 [4.050059] input: ASIX Electronics AX68002 as /devices/pci:00/:00:14.0/usb1/1-8/1-8.6/1-8.6:1.1/0003:0B95:6801.0008/input/input9 [4.050106] input: ASIX Electronics AX68002 System Control as /devices/pci:00/:00:14.0/usb1/1-8/1-8.6/1-8.6:1.1/0003:0B95:6801.0008/input/input10 [4.065829] pstore: Using compression: deflate [4.065839] pstore: Registered efi as persistent store backend [4.066710] asus_wmi: ASUS WMI generic driver loaded [4.067241] asus_wmi: Initialization: 0x0 [4.067256] asus_wmi: BIOS WMI version: 0.9 [4.067299] asus_wmi: SFUN value: 0x0 [4.067479] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input12 [4.078487] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [4.078488] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.078489] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [4.078489] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.078490] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x11/0x0 [4.078490] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.078491] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [4.078492] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [4.078492] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a [4.107645] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1f.3/sound/card0/input13 [4.108662] input: ASIX Electronics AX68002 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-8/1-8.6/1-8.6:1.1/0003:0B95:6801.0008/input/input11 [4.108740] asus_wmi: Number of fans: 1 [4.115139] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1f.3/sound/card0/input14 [4.115163] hid-generic 0003:0B95:6801.0008: input,hidraw4: USB HID v1.10 Mouse [ASIX Electronics AX68002] on usb-:00:14.0-8.6/input1 [4.115205] input: HDA Intel PCH Line as /devices/pci:00/:00:1f.3/sound/card0/input15 [4.116117] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input16 [4.116177] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1f.3/sound/card0/input17 [4.176162] systemd-journald[318]: Received request to flush runtime journal from PID 1 [4.254877] logitech-djreceiver 0003:046D:C52B.0006: hiddev1,hidraw5: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-8.2/input2 [4.255132] intel_rapl:
