On Tue, Dec 15, 2020 at 6:28 PM Sébastien Luttringer [off-list ref] wrote:

On Tue, 2020-12-15 at 15:53 -0800, Song Liu wrote:

quoted

On Tue, Dec 15, 2020 at 10:40 AM Sébastien Luttringer [off-list ref]
wrote:


Hi,

I am very sorry for this problem. This is a bug in 5.10 which is fixed
in 5.10.1.
To fix it, please upgrade your kernel to 5.10.1 (or downgrade to previous
version). In many cases, the array should be back normal. If not, please try

       mdadm --grow --size <size> /dev/mdXXX.

If the original array uses the full disk/partition, you can use "max" for
<size>
to safe some calculation.

Please let me know if you have future problem with it.

Hello,

The array didn't returned to normal after a reboot on 5.10.1. The `mdadm --grow
--size max /dev/md0` command did the trick. The e2fsck detect no error, so we
are back online.

Thanks you for your help and especially your quick answer.

I am glad that helped.

Song