From: Eric Valette <eric.valette@free.fr>
To: Shaohua Li <shli@kernel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Problem with array raid10 array resync on 4.4.0 (keeps reyncing each reboot)
Date: Thu, 4 Feb 2016 07:57:47 +0100 [thread overview]
Message-ID: <56B2F66B.2020102@free.fr> (raw)
In-Reply-To: <20160204011731.GA29132@kernel.org>
On 04/02/2016 02:17, Shaohua Li wrote:
> On Mon, Feb 01, 2016 at 12:00:36AM +0100, Eric Valette wrote:
>> On 28/01/2016 20:52, Eric Valette wrote:
>>> On 28/01/2016 19:25, Shaohua Li wrote:
>>>
>>> If really needed can rebuild a 4.4 kernel and boot it. What do you mean
>>> by special config? I can send you my kernel .config once rebuild
>>> (oldconfig from 4.1.16)
>>
>> Linux nas2 4.4.1 #1 SMP Sun Jan 31 23:46:26 CET 2016 x86_64 GNU/Linux
>
> Nothing useful. Did you try stop the array and reassemble it in 4.4 and check
> if resync runs? I can only imagine the reboot script didn't clean shutdown the
> array and trigger the issue. A stop/reassemble circle will tell us if this is
> the issue.
If the issue was in the script it would happen with all the kernel
version no? Si far 3.14, 3.18, 4.1 works correctly (when upgrading).
Only 4.4 fails.
4.4 in fact seems to fails to boot the first time I boot it. As I have
no console normally, I have to shut down via power button and then it
resync. I can understand this behavior but not
1) that the resync fails each time and
2) that it fails to boot the first time I change for a 4.4 kernel.
-- eric
prev parent reply other threads:[~2016-02-04 6:57 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
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 [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=56B2F66B.2020102@free.fr \
--to=eric.valette@free.fr \
--cc=linux-raid@vger.kernel.org \
--cc=shli@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).