small mdadm issue under debian

small mdadm issue under debian

[Thomas Fjellstrom]

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.

-- 
Thomas Fjellstrom
tfjellstrom@shaw.ca

Re: small mdadm issue under debian

[Thomas Fjellstrom]

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

Re: small mdadm issue under debian

[Majed B.]

When using newer kernels, did you update initrd?

sudo update-initramfs -u -k all

Then reboot to a new kernel and see if it auto assembles.

On Thu, Oct 29, 2009 at 10:30 AM, Thomas Fjellstrom <tfjellstrom@shaw.ca> wrote:
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
       Majed B.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: small mdadm issue under debian

[Thomas Fjellstrom]

On Thu October 29 2009, Majed B. wrote:
> When using newer kernels, did you update initrd?
> 
> sudo update-initramfs -u -k all

Yes I did.

> Then reboot to a new kernel and see if it auto assembles.

I don't have them auto assemble in initrd/initramfs. Its done later in the 
mdadm-raid script if I read it correctly. Its also a 1.1 metadata array, so 
the kernel can't auto assemble it itself.

Just somehow it fails to build under 2.6.29+ but works fine under 2.6.26 
with the same userspace.

> On Thu, Oct 29, 2009 at 10:30 AM, Thomas Fjellstrom <tfjellstrom@shaw.ca> 
wrote:
> > 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
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-raid"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
Thomas Fjellstrom
tfjellstrom@shaw.ca

Re: small mdadm issue under debian

[Thomas Fjellstrom]

On Thu October 29 2009, Asdo wrote:
> Thomas Fjellstrom wrote:
> >> Then reboot to a new kernel and see if it auto assembles.
> >
> > I don't have them auto assemble in initrd/initramfs. Its done later in
> > the mdadm-raid script if I read it correctly. Its also a 1.1 metadata
> > array, so the kernel can't auto assemble it itself.
> 
> You probably mean "it can't auto assemble it itself without an
> initramfs"! :-D

Maybe I'm being a little pedantic, but initramfs is a miniature userspace so 
it isn't the kernel that is doing the auto assembling ;) just an embedded 
mdadm ;)
 
> I have my root filesystem on a 1.0 metadata raid on 2.6.31 so it
> definitely assembles it...
> For 1.1 I suppose it's the same.
> But it does need to be in the /etc/mdadm/mdadm.conf that is packed in
> the initramfs, so make sure the problem is not that one, try by
> unpacking the initramfs with cpio
> 

I don't need it to assemble my array at boot time, the array is used for 
media files, not the root partition. I would however like the mdadm-raid 
script to be able to assemble the array during boot, which works under 
2.6.26, and not under 2.6.29,.30, or .31.

-- 
Thomas Fjellstrom
tfjellstrom@shaw.ca

Re: small mdadm issue under debian

[Neil Brown]

On Thursday October 29, tfjellstrom@shaw.ca 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.

Me too.

Can you run the "mdadm" command that fails by hand and have it still
fail?
If so, can you run it with "-v" and post the result.
Or maybe edit the script to add -v and see what it says.

NeilBrown 

Re: small mdadm issue under debian

[Thomas Fjellstrom]

On Sun November 1 2009, you wrote:
> On Thursday October 29, tfjellstrom@shaw.ca 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.
> 
> Me too.
> 
> Can you run the "mdadm" command that fails by hand and have it still
> fail?
> If so, can you run it with "-v" and post the result.
> Or maybe edit the script to add -v and see what it says.

I meant to get around to this, but it seems I had to "fast track" the 
building of my new server, and it necessitated two new hard disks (raid0) 
and a new debian install. And so far, it seems both the raid1 root, and 
raid5 data arrays are properly building and mounting.

Sorry for the noise. If I see it again I'll try and figure it out.

The only hint I might have is that it might have fixed itself when I added 
raid5 to the initramfs modules file. Not sure though.

> NeilBrown
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
Thomas Fjellstrom
tfjellstrom@shaw.ca