Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #67355 > unrolled thread

Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5)

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5) Ben Hutchings <ben@decadent.org.uk> - 2020-06-21 23:00 +0200
    Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5) eric gdr <eric.gdr@gmail.com> - 2020-06-22 07:20 +0200

#67355 — Bug#963239: linux-image-4.19.0-9-amd64: software raid array resync at boot (raid5)

[Multipart message — attachments visible in raw view] — view raw

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.

[toc] | [next] | [standalone]

#67356

[Multipart message — attachments visible in raw view] — view raw

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 <ben@decadent.org.uk> 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.
>
>
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web