From: Song Liu <song@kernel.org>
To: "Sébastien Luttringer" <seblu@seblu.net>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Array size dropped from 40TB to 7TB when upgrading to 5.10
Date: Tue, 15 Dec 2020 20:28:17 -0800 [thread overview]
Message-ID: <CAPhsuW4zE+a0rh6f+tFeM8QcW6GP2evd03X89agxrm0=WpDTxw@mail.gmail.com> (raw)
In-Reply-To: <5d57edd9de751d009023407666f97e72a31f1459.camel@seblu.net>
On Tue, Dec 15, 2020 at 6:28 PM Sébastien Luttringer <seblu@seblu.net> wrote:
>
>
> 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@seblu.net>
> > 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
prev parent reply other threads:[~2020-12-16 4:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 18:29 Array size dropped from 40TB to 7TB when upgrading to 5.10 Sébastien Luttringer
2020-12-15 23:53 ` Song Liu
2020-12-16 2:20 ` Sébastien Luttringer
2020-12-16 4:28 ` Song Liu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPhsuW4zE+a0rh6f+tFeM8QcW6GP2evd03X89agxrm0=WpDTxw@mail.gmail.com' \
--to=song@kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=seblu@seblu.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).