From: Roman Mamedov <rm@romanrm.net>
To: Bogo Mipps <bogo.mipps@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Advice please re failed Raid6
Date: Sun, 16 Jul 2017 05:58:08 +0500 [thread overview]
Message-ID: <20170716055808.4b96b4bc@natsu> (raw)
In-Reply-To: <9dca5b7a-b60e-0e93-41fd-49d092d8b27b@gmail.com>
Hello,
One thing that I spotted:
Jun 27 16:52:21 keruru kernel: [ 2.922808] md: kicking non-fresh sdb from array!
Jun 27 16:52:21 keruru kernel: [ 3.173236] md/raid:md0: device sdd operational as raid disk 1
Jun 27 16:52:21 keruru kernel: [ 3.173239] md/raid:md0: device sde operational as raid disk 3
Jun 27 16:52:21 keruru kernel: [ 3.173242] md/raid:md0: device sdc operational as raid disk 2
The disk order here was "b d c e"
Jul 6 09:45:52 keruru kernel: [ 1195.580003] md/raid:md0: device sdb operational as raid disk 0
Jul 6 09:45:52 keruru kernel: [ 1195.580012] md/raid:md0: device sde operational as raid disk 3
Jul 6 09:45:52 keruru kernel: [ 1195.580018] md/raid:md0: device sdd operational as raid disk 2
Jul 6 09:45:52 keruru kernel: [ 1195.580025] md/raid:md0: device sdc operational as raid disk 1
But here the order changes to "b c d e"
Unless this is across reboots and your hardware detects disks in a random
order, something weird is going on here.
Also, your array has creation time of "Fri Jun 30 15:42:27 2017", but you
provide no dmesg or logs from that date.
Maybe you forgot to use --assume-clean on one of the attempts (and that's when
you nuked the array entirely)?
Or perhaps --assume-clean also rewrites the creation date, I am not sure.
--
With respect,
Roman
next prev parent reply other threads:[~2017-07-16 0:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 23:40 Advice please re failed Raid6 Bogo Mipps
2017-07-16 0:58 ` Roman Mamedov [this message]
2017-07-17 0:19 ` Peter Grandi
2017-07-19 1:52 ` Bogo Mipps
2017-07-19 12:36 ` Peter Grandi
2017-07-20 3:59 ` Bogo Mipps
[not found] ` <cf9aac00-91b3-3cb5-bceb-df5d7113b933@gmail.com>
2017-07-21 0:44 ` Bogo Mipps
2017-07-21 9:48 ` Peter Grandi
2017-07-23 0:13 ` Bogo Mipps
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=20170716055808.4b96b4bc@natsu \
--to=rm@romanrm.net \
--cc=bogo.mipps@gmail.com \
--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