Re: Array size dropped from 40TB to 7TB when upgrading to 5.10

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2020-12-15 at 15:53 -0800, Song Liu wrote:
> On Tue, Dec 15, 2020 at 10:40 AM Sébastien Luttringer <seblu@xxxxxxxxx>
> 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.


Sébastien "Seblu" Luttringer

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux