linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: lists@xunil.at
Cc: linux-raid@vger.kernel.org
Subject: Re: Re-adding disks to RAID6 in a Fujitsu NAS: old mdadm?
Date: Thu, 28 Jun 2012 21:22:57 +1000	[thread overview]
Message-ID: <20120628212257.5ca8fb05@notabene.brown> (raw)
In-Reply-To: <4FEC2071.8010504@xunil.at>

[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]

On Thu, 28 Jun 2012 11:14:25 +0200 "Stefan G. Weichinger" <lists@xunil.at>
wrote:

> Am 28.06.2012 10:59, schrieb Stefan G. Weichinger:
> 
> >> If you have a machine with the same arch at the NAS, you could
> >>
> >> git clone git://neil.brown.name/mdadm -b mdadm-2.6.5 cd mdadm make
> >> mdadm.static CWFLAGS=-Wall
> >>
> >> and then use the "mdadm.static" on the NAS.
> > 
> > Ok, thanks. I could boot some ubuntu on my Atom-netbook .. or what?
> > Would it be enough to match the 64bit-environment, or would I have to
> > use something with the same kernel ... ?
> 
> Update:
> 
> compiled mdadm.static on a 32bit machine and could re-add the two
> partitions to the array! cool! thanks, Neil!
> 
> ~500 mins to wait now.
> 
> Do I have to fear read-errors as with RAID5 now?

If you get a read error, then that block in the new devices cannot be
recovered, so the recovery will abort.  But you have nothing to fear except
fear itself :-)

> 
> I still don't fully understand if there are also 2 bits of
> parity-informations available in a degraded RAID6 array on 2 disks only.

In a 4-drive RAID6 like yours, each stripe contains 2 data blocks and 2
parity blocks (Called 'P' and 'Q').
When two devices are failed/missing, some stripes will have 2 data blocks and
no parity, some will have both parity blocks and no data (but can of course
compute the data blocks from the parity blocks). Some will have one of each.

Does that answer the question?

NeilBrown


> 
> Thanks again so far, hoping the best now ;-)
> 
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2012-06-28 11:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 13:57 Re-adding disks to RAID6 in a Fujitsu NAS: old mdadm? Stefan G. Weichinger
2012-06-27 10:17 ` Stefan G. Weichinger
2012-06-27 11:34   ` Stefan G. Weichinger
2012-06-27 11:38     ` Stefan G. Weichinger
2012-06-28  6:32 ` NeilBrown
2012-06-28  8:59   ` Stefan G. Weichinger
2012-06-28  9:14     ` Stefan G. Weichinger
2012-06-28  9:23       ` Stefan G. Weichinger
2012-06-28 11:22       ` NeilBrown [this message]
2012-06-28 15:56         ` Stefan G. Weichinger
2012-06-28 18:25           ` Stefan G. Weichinger
2012-06-28 21:36             ` NeilBrown
2012-06-29  8:18               ` Stefan G. Weichinger
2012-07-02  8:30                 ` Stefan G. Weichinger
2012-06-28 21:39           ` NeilBrown
2012-06-28  9:39     ` NeilBrown
2012-06-28  9:42       ` Stefan G. Weichinger

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=20120628212257.5ca8fb05@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@xunil.at \
    /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).