All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Florian D." <flockmock@gmx.at>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cannot add device to partitioned raid6 array
Date: Sun, 01 Apr 2007 09:25:27 +0000	[thread overview]
Message-ID: <460F7A87.3030201@gmx.at> (raw)
In-Reply-To: <17935.8101.815473.709581@notabene.brown>

Neil Brown wrote:
> On Saturday March 31, flockmock@gmx.at wrote:
>> hi list!
>>
>> in short:
>> I created a partitioned raid6 array with 2 missing drives. Now, I want to add a device. It fails with:
>> flockmock ~ # mdadm -a /dev/md_d4 /dev/sdb2
>> mdadm: add new device failed for /dev/sdb2 as 4: Invalid argument
> 
> Thanks for the detailed problem report.
> 
> I think the cause of the error is that /dev/sdb2 is too small.
> It needs to be at least 490030594 sectors. How big is it?

but the *device* size should be only ~250GB, so the array size is ~500GB, no?

flockmock ~ # mdadm --detail /dev/md_d4
/dev/md_d4:
         Version : 00.90.03
   Creation Time : Sat Mar 31 19:48:58 2007
      Raid Level : raid6
      Array Size : 490030464 (467.33 GiB 501.79 GB)
   Used Dev Size : 245015232 (233.66 GiB 250.90 GB)
                   ^^^^^^^^^^

these disks are all 250 GB harddisks, formatted in the same way -- but they are from different 
vendors! The block sizes from the partitions vary a little bit (taken from /sbin/fdisk):

/dev/sda2: 245015347
/dev/sdc2: 245015347
/dev/sdb2: 244099642  -> different vendor

do you think that may be the cause?

thanks a lot,
florian


  reply	other threads:[~2007-04-01  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-31 23:44 cannot add device to partitioned raid6 array Florian D.
2007-04-01  2:57 ` Neil Brown
2007-04-01  9:25   ` Florian D. [this message]
2007-04-01 10:07     ` Neil Brown
2007-04-01 11:23       ` Florian D.

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=460F7A87.3030201@gmx.at \
    --to=flockmock@gmx.at \
    --cc=linux-kernel@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 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.