linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michele Bonera <mbonera@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Problems after reshaping of Raid5 array
Date: Tue, 30 Nov 2010 08:23:00 +0100	[thread overview]
Message-ID: <1291101780.15141.4.camel@bellatrix.morrisoft.local> (raw)
In-Reply-To: <20101130084501.702e7486@notabene.brown>

Il giorno mar, 30/11/2010 alle 08.45 +1100, Neil Brown ha scritto:

> > Yesterday evening I added another WD, this time an EARS
> > (512 byte sectors): I created a partition on it, respecting the

Just to be precise: 4K byte sector (my mistake).

> Yes.
> I think you can fix it by simply failing and removing sdc
> Then md/raid5 will recover that data using the parity block, and that should
> be correct.
> It appears that the partition you created on the new device started at a
> multiple of 64K.  When this happen, the superblock at the end of the
> partition also looks valid when seen at the end of the whole device.
> Somehow mdadm got confused and choose the whole device (sdc) instead of the
> partition (sdc1).

I did it and it worked! Thanks a lot Neil!!!

> I am surprised at this because since mdadm-2.5.1, mdadm will refuse to
> assemble an array if it sees two devices that appear to have the same
> superblock.  Could you possibly be using something that old??

The distribution is Ubuntu Server 10.04, 
kernel 2.6.32-26-generic-pae, mdadm 2.6.7.1

Again many thanks Neil, you saved me! :)

Cheers,
--
Michele Bonera
linux user group brescia


  reply	other threads:[~2010-11-30  7:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 17:24 Problems after reshaping of Raid5 array Michele Bonera
2010-11-29 19:12 ` Jan Ceuleers
2010-11-29 20:04   ` Michele Bonera
2010-11-30 17:00     ` Jan Ceuleers
2010-11-29 21:45 ` Neil Brown
2010-11-30  7:23   ` Michele Bonera [this message]
2010-11-30 19:45     ` Jan Ceuleers
2010-12-03  7:03       ` Michele Bonera

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=1291101780.15141.4.camel@bellatrix.morrisoft.local \
    --to=mbonera@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).