md: bug in file drivers/md/md.c, line 1513

md: bug in file drivers/md/md.c, line 1513

[Paul Slootman]

This is on kernel 2.6.11, mdadm 1.4.0

The system has MD devices that are auto-configured on boot.

However, there are also devices connected via another SCSI adapter
(actually, a Qlogic QLA2300). I'm using a module for that. As the
auto-configure only runs at boot (or rather, when the md subsystem is
started).  I wanted to restart a raid-0 device that I had previously
created. I did:

	mdadm --run /dev/md10

as a simple attempt to see what would happen. What happened was the
error message in the subject, and a "COMPLETE RAID STATE PRINTOUT"...
In that output there is a line "md10:", the next line is
"md1: <sde1><sdd1><sdc1><sdb1><sda1>".


Admittedly the usage may be wrong, but having the kernel say "bug" can't
be right :-)


Paul Slootman

Re: md: bug in file drivers/md/md.c, line 1513

[Neil Brown]

On Tuesday March 22, paul+nospam@wurtel.net wrote:
> This is on kernel 2.6.11, mdadm 1.4.0
> 
> The system has MD devices that are auto-configured on boot.
> 
> However, there are also devices connected via another SCSI adapter
> (actually, a Qlogic QLA2300). I'm using a module for that. As the
> auto-configure only runs at boot (or rather, when the md subsystem is
> started).  I wanted to restart a raid-0 device that I had previously
> created. I did:
> 
> 	mdadm --run /dev/md10

As you admit, this is wrong.  You want something like
  mdadm --assemble /dev/md10 /dev/.....(list of component devices)

or describe the md10 array (e.g. via UUID) in /etc/mdadm.conf

> 
> as a simple attempt to see what would happen. What happened was the
> error message in the subject, and a "COMPLETE RAID STATE PRINTOUT"...
> In that output there is a line "md10:", the next line is
> "md1: <sde1><sdd1><sdc1><sdb1><sda1>".
> 
> 
> Admittedly the usage may be wrong, but having the kernel say "bug" can't
> be right :-)
> 

Yes, there are quite a few of those silly bug messages.  I've removed
a few, but have not yet gone through and checked and removed all the
bad ones.
NeilBrown

Re: md: bug in file drivers/md/md.c, line 1513

[Paul Slootman]

On Thu 24 Mar 2005, Neil Brown wrote:
> On Tuesday March 22, paul+nospam@wurtel.net wrote:
> > This is on kernel 2.6.11, mdadm 1.4.0
> > 
> > The system has MD devices that are auto-configured on boot.
> > 
> > However, there are also devices connected via another SCSI adapter
> > (actually, a Qlogic QLA2300). I'm using a module for that. As the
> > auto-configure only runs at boot (or rather, when the md subsystem is
> > started).  I wanted to restart a raid-0 device that I had previously
> > created. I did:
> > 
> > 	mdadm --run /dev/md10
> 
> As you admit, this is wrong.  You want something like
>   mdadm --assemble /dev/md10 /dev/.....(list of component devices)
> 
> or describe the md10 array (e.g. via UUID) in /etc/mdadm.conf

It took a bit of trial and error (I find the mdadm docs a bit
confusing...) but I came up with this:

mdadm --assemble --super-minor=10 --config=partitions /dev/md10


> > error message in the subject, and a "COMPLETE RAID STATE PRINTOUT"...
> > In that output there is a line "md10:", the next line is
> > "md1: <sde1><sdd1><sdc1><sdb1><sda1>".
> > 
> > 
> > Admittedly the usage may be wrong, but having the kernel say "bug" can't
> > be right :-)
> > 
> 
> Yes, there are quite a few of those silly bug messages.  I've removed
> a few, but have not yet gone through and checked and removed all the
> bad ones.

Keep up the good work :-)


Paul Slootman