linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shli@kernel.org>
To: Eric Valette <eric.valette@free.fr>
Cc: linux-raid@vger.kernel.org
Subject: Re: Problem with array raid10 array resync on 4.4.0 (keeps reyncing each reboot)
Date: Thu, 28 Jan 2016 10:25:22 -0800	[thread overview]
Message-ID: <20160128182522.GB23378@kernel.org> (raw)
In-Reply-To: <56A870AD.4070400@free.fr>

On Wed, Jan 27, 2016 at 08:24:29AM +0100, Eric Valette wrote:
> On 27/01/2016 00:31, Shaohua Li wrote:
> >On Tue, Jan 26, 2016 at 03:49:42PM +0100, Eric Valette wrote:
> >>Hi,
> >>
> >>My raid 10 array (5 disk with one spare) was doing a  resync after an
> >>upgrade to 4.4.0 from 4.1.15. The resync progress was steady and at the end
> >>the /proc/mdstat was apparently complete but when rebooting, it started
> >>resycing over and over. I noticed my dmesg was totally filled with raid10
> >>conf printout message so it was impossible to trace anything else.
> >>
> >>Did a resync test with 3.14.58 (because I knew it had worked for resync
> >>before and was still available as a boot option)  and the array was
> >>correctly rebuild.
> >>Runs fine with 4.1.16 now.
> >>
> >>Please CC me as I'm not subscribed.
> >
> >Could you please provide more info, like mdadm -D /dev/md0 in v4.4? If you run
> >a stop/reassemble, does the resync start?
> 
> I'm not going to retry kernel 4.4.0 on this device as I'm no more confident
> about raid10 support with this 4.4 version.

Thanks! I know switching to a kernel which is not working well is risky, but
the info from 4.1 doesn't have enough info for debuging. I also tried to
reproduce the issue locally, but no success. Did you have any other info which
could help debugging, for example special config?

Thanks,
Shaohua

  reply	other threads:[~2016-01-28 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 14:49 Problem with array raid10 array resync on 4.4.0 (keeps reyncing each reboot) Eric Valette
2016-01-26 23:31 ` Shaohua Li
2016-01-27  7:24   ` Eric Valette
2016-01-28 18:25     ` Shaohua Li [this message]
2016-01-28 19:52       ` Eric Valette
2016-01-31 23:00         ` Eric Valette
2016-02-04  1:17           ` Shaohua Li
2016-02-04  6:57             ` Eric Valette

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=20160128182522.GB23378@kernel.org \
    --to=shli@kernel.org \
    --cc=eric.valette@free.fr \
    --cc=linux-raid@vger.kernel.org \
    /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).