All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Florian D." <flockmock@gmx.at>
To: linux-kernel@vger.kernel.org
Subject: cannot add device to partitioned raid6 array
Date: Sat, 31 Mar 2007 23:44:35 +0000	[thread overview]
Message-ID: <460EF263.7020505@gmx.at> (raw)

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

I think it is the same problem as in:
http://marc.info/?l=linux-raid&m=115316147716600&w=2



details:
kernel 2.6.20.4
mdadm-2.6.1
the raid6 array:

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)
    Raid Devices : 4
   Total Devices : 2
Preferred Minor : 4
     Persistence : Superblock is persistent

     Update Time : Sat Mar 31 23:28:37 2007
           State : clean, degraded
  Active Devices : 2
Working Devices : 2
  Failed Devices : 0
   Spare Devices : 0

      Chunk Size : 32K

            UUID : dfb5e536:2447b984:b7699fd8:8ba37cbf
          Events : 0.2972

     Number   Major   Minor   RaidDevice State
        0       8        2        0      active sync   /dev/sda2
        1       8       34        1      active sync   /dev/sdc2
        2       0        0        2      removed
        3       0        0        3      removed

the device, which I want to add:
flockmock ~ # mdadm -E /dev/sdb2
/dev/sdb2:
           Magic : a92b4efc
         Version : 00.90.00
            UUID : dfb5e536:2447b984:b7699fd8:8ba37cbf
   Creation Time : Sat Mar 31 19:48:58 2007
      Raid Level : raid6
   Used Dev Size : 245015232 (233.66 GiB 250.90 GB)
      Array Size : 490030464 (467.33 GiB 501.79 GB)
    Raid Devices : 4
   Total Devices : 2
Preferred Minor : 4

     Update Time : Sat Mar 31 23:29:23 2007
           State : clean
  Active Devices : 2
Working Devices : 2
  Failed Devices : 2
   Spare Devices : 0
        Checksum : 8aeeef56 - correct
          Events : 0.2974

      Chunk Size : 32K

       Number   Major   Minor   RaidDevice State
this     4       8       18       -1      spare   /dev/sdb2

    0     0       8        2        0      active sync   /dev/sda2
    1     1       8       34        1      active sync   /dev/sdc2
    2     2       0        0        2      faulty removed
    3     3       0        0        3      faulty removed

dmesg shows such error mesgs:
[  220.681135] md: sdb2 has invalid sb, not importing!
[  220.681186] md: md_import_device returned -22
[  220.681435] md: sdb2 has invalid sb, not importing!
[  220.681463] md: md_import_device returned -22

any idea how to resolve this? thanks,
florian

PS: please cc me in replies, thanks.

             reply	other threads:[~2007-04-01  0:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-31 23:44 Florian D. [this message]
2007-04-01  2:57 ` cannot add device to partitioned raid6 array Neil Brown
2007-04-01  9:25   ` Florian D.
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=460EF263.7020505@gmx.at \
    --to=flockmock@gmx.at \
    --cc=linux-kernel@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 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.