linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Landman <landman@scalableinformatics.com>
To: linux-raid@vger.kernel.org
Subject: question on how to update the super-minor
Date: Thu, 19 Aug 2010 17:00:13 -0400	[thread overview]
Message-ID: <4C6D9B5D.8080705@scalableinformatics.com> (raw)

Hi folks

   Moved an array to a new machine.  For a number or reasons, the arrays 
which were md0 and md1, are now md1 and md2.

   I can force the assembly of the arrays, but can't force them to 
autoassemble, and it looks like the minors are wrong.

  ~ # mdadm --assemble /dev/md2 --update=super-minor  /dev/sdc2 /dev/sde2
mdadm: /dev/md2 has been started with 2 drives.

  ~ # mdadm --assemble --update=super-minor /dev/md1 /dev/sdd2 /dev/sdf2
mdadm: /dev/md1 has been started with 2 drives.

  ~ # mdadm --examine --scan
ARRAY /dev/md/0 metadata=1.0 UUID=6ddbf291:a7344bb6:375a9f38:89b409e9 
name=jr5.scalableinformatics.com:0
ARRAY /dev/md/0 metadata=1.2 UUID=2e8b8744:16f038fa:9c4ba1b1:d4a7ee79 name=0
ARRAY /dev/md/1 metadata=1.2 UUID=04251ae2:ef750917:f71c67b8:152b985b name=1

~ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid0 sdf2[0] sdd2[1]
       14352793600 blocks super 1.2 2048k chunks

md2 : active raid0 sde2[0] sdc2[1]
       1923825664 blocks super 1.2 1024k chunks

md0 : active raid1 sda1[0] sdb1[1]
       26217400 blocks super 1.0 [2/2] [UU]
       bitmap: 0/201 pages [0KB], 64KB chunk

unused devices: <none>

How do I force the md1 and md2 to accept the new minors?  The 
--update=super-minor isn't working on assembly.

Also, for completeness

~ # cat /etc/mdadm.conf
DEVICE containers partitions
ARRAY /dev/md0 UUID=6ddbf291:a7344bb6:375a9f38:89b409e9
name=jr5.scalableinformatics.com:0
ARRAY /dev/md1 metadata=1.2 UUID=2e8b8744:16f038fa:9c4ba1b1:d4a7ee79 name=1
ARRAY /dev/md2 metadata=1.2 UUID=04251ae2:ef750917:f71c67b8:152b985b name=2

~ # mdadm --examine /dev/sdf2
/dev/sdf2:
           Magic : a92b4efc
         Version : 1.2
     Feature Map : 0x0
      Array UUID : 04251ae2:ef750917:f71c67b8:152b985b
            Name : 1
   Creation Time : Sun Feb 15 06:21:14 2009
      Raid Level : raid0
    Raid Devices : 2

  Avail Dev Size : 14352796387 (6843.95 GiB 7348.63 GB)
   Used Dev Size : 0
     Data Offset : 16 sectors
    Super Offset : 8 sectors
           State : active
     Device UUID : 80406a02:959d30ee:9d090fd5:c570c9f7

     Update Time : Sun Feb 15 06:21:14 2009
        Checksum : 5e70dc7e - correct
          Events : 0

      Chunk Size : 2048K

    Device Role : Active device 0
    Array State : AA ('A' == active, '.' == missing)



-- 
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: landman@scalableinformatics.com
web  : http://scalableinformatics.com
        http://scalableinformatics.com/jackrabbit
phone: +1 734 786 8423 x121
fax  : +1 866 888 3112
cell : +1 734 612 4615

             reply	other threads:[~2010-08-19 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 21:00 Joe Landman [this message]
2010-08-19 21:40 ` question on how to update the super-minor Neil Brown

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=4C6D9B5D.8080705@scalableinformatics.com \
    --to=landman@scalableinformatics.com \
    --cc=linux-raid@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 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).