All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: John Crisp <jcrisp@safeandsoundit.co.uk>,
	linux-raid@vger.kernel.org, Phil Turmel <philip@turmel.org>,
	NeilBrown <neilb@suse.com>
Subject: Re: Raid 6 recovery
Date: Sat, 4 Nov 2017 12:46:58 +0000	[thread overview]
Message-ID: <59FDB6C2.1040800@youngman.org.uk> (raw)
In-Reply-To: <778940c7-cd7c-bda7-4db6-1e1b605a9557@safeandsoundit.co.uk>

On 03/11/17 10:44, John Crisp wrote:
> On 03/11/17 00:47, Wols Lists wrote:
>> On 31/10/17 18:11, Wols Lists wrote:
>>> It's possible - I wouldn't know - that the existence of the MBR stops
>>> mdadm looking for a superblock that applies to the whole drive, which
>>> could explain why those drives have disappeared.
>>
>> Just been digging in the code - function check_raid - I think if you
>> pass a drive to mdadm it checks the drive for a superblock, and doesn't
>> look for whether a partition table exists. So I think that's that
>> explanation blown out the water ... :-(
>>
> 
> :-) Thanks for looking.
> 
> As I mentioned, I think I created the array via Xubuntu.
> 
> As far as I remember I didn't partition any of the drives - just added
> them to the array and I think it effectively created one partition
> across the whole array (which would make sense why you can't see
> partitions on individual drives)
> 
> I am pretty sure that is trashed, but I like to try and understand these
> things !
> 
More for Neil, this, but I've had a nasty thought. Did you reboot at all
(as in clean shutdown, not crash and restart) at any point during this?
I get the impression you might not have.

Because that *could* explain the missing superblocks! I think raid
updates the superblock every time it moves the rebuild window, so it
should get rewritten to disk regularly. BUT. Is it possible that it was
sitting in the disk cache when the system crashed?

I find it hard to believe that's the case, but it could explain at least
some of it (doesn't explain why those drives had mbr's, though).

Cheers,
Wol


  reply	other threads:[~2017-11-04 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 15:42 Raid 6 recovery John Crisp
2017-10-31 16:27 ` Wols Lists
2017-10-31 17:42   ` John Crisp
2017-10-31 18:11     ` Wols Lists
2017-11-02 23:47       ` Wols Lists
2017-11-03 10:44         ` John Crisp
2017-11-04 12:46           ` Wols Lists [this message]
2017-11-05 17:13             ` John Crisp
2017-11-05 18:08               ` Wol's lists

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=59FDB6C2.1040800@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=jcrisp@safeandsoundit.co.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=philip@turmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.