All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: small mdadm issue under debian
Date: Thu, 29 Oct 2009 01:30:18 -0600	[thread overview]
Message-ID: <200910290130.18829.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <200910290124.59090.tfjellstrom@shaw.ca>

On Thu October 29 2009, Thomas Fjellstrom wrote:
> I've been trying to get mdadm to auto assemble my raid array for a while
> now, and as I'm trying to test which kernels give me back some
>  performance (testing 2.6.26 right now), I find that with this kernel,
>  its happily auto assembling my 1.1 versioned metadata array. 3.6.30 does
>  not, nor does .31 or .32 for that matter. Same version of mdadm, for
>  some reason, when the mdadm-raid init script is run, it fails to
>  assemble the raid array I've specified in mdadm.conf. And again, it
>  automagically works with 2.6.26.
> 
> color me confused.
> 

I totally forgot:

root@natasha:/home/moose# mdadm --version
mdadm - v3.0.3 - 22nd October 2009

root@natasha:/home/moose# uname -a
Linux natasha 2.6.26-2-amd64 #1 SMP Wed Aug 19 22:33:18 UTC 2009 x86_64 
GNU/Linux

root@natasha:/home/moose# mdadm -D /dev/md0
/dev/md0:
        Version : 1.01
  Creation Time : Wed Oct 14 08:55:25 2009
     Raid Level : raid5
     Array Size : 3907049472 (3726.05 GiB 4000.82 GB)
  Used Dev Size : 976762368 (931.51 GiB 1000.20 GB)
   Raid Devices : 5
  Total Devices : 5
    Persistence : Superblock is persistent

    Update Time : Thu Oct 29 01:28:10 2009
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : natasha:0  (local to host natasha)
           UUID : 7d0e9847:ec3a4a46:32b60a80:06d0ee1c
         Events : 4952

    Number   Major   Minor   RaidDevice State
       0       8       64        0      active sync   /dev/sde
       1       8       80        1      active sync   /dev/sdf
       2       8       32        2      active sync   /dev/sdc
       3       8       48        3      active sync   /dev/sdd
       5       8       96        4      active sync   /dev/sdg


And I'm running Debian Sid.

-- 
Thomas Fjellstrom
tfjellstrom@shaw.ca

  reply	other threads:[~2009-10-29  7:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29  7:24 small mdadm issue under debian Thomas Fjellstrom
2009-10-29  7:30 ` Thomas Fjellstrom [this message]
2009-10-29 12:26   ` Majed B.
2009-10-29 17:20     ` Thomas Fjellstrom
     [not found]       ` <4AE9D337.30609@shiftmail.org>
2009-10-29 18:04         ` Thomas Fjellstrom
2009-11-02  2:03 ` Neil Brown
2009-11-06 21:18   ` Thomas Fjellstrom

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=200910290130.18829.tfjellstrom@shaw.ca \
    --to=tfjellstrom@shaw.ca \
    --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 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.