All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Glamm <glamm@a-s-i.com>
To: linux-raid@vger.kernel.org
Subject: RAID migration from 2.4 -> 2.6
Date: Thu, 12 Aug 2004 10:29:39 -0500	[thread overview]
Message-ID: <20040812152939.GD5326@romulus.a-s-i.com> (raw)

At the moment I'm stumped, so I wonder if someone might be able
to give me a hand.

First, my RAID setup: I have a pair of Adaptec 7899 controllers
with five 9GB SCSI disks on each.  The first disks on each controller
are allocated in a RAID 1 configuration for boot, swap, /usr, etc.,
while the next three disks on each controller are allocated in
a RAID 5 configuration to our running services and data.  The last
disk on each controller is designated as a spare disk for each RAID.

These RAIDs work well with 2.4.  I've got them configured
for autodetect, so the system brings them up at startup in 2.4.

Now I'm trying to migrate to 2.6.7, and autodetection basically
ignores all my SCSI disks.  I get three lines:

  Autodetecting RAID arrays:
    ..  autodetecting
  Done.

when I try to boot 2.6.7.  (Additional note: all SCSI controllers
and disks are discovered just fine, although I am using the new
Adaptec driver in 2.6.)

In the course of googling/reading to fix this problem, I've
come up with several possibilities:

  1) My 2.4 setup uses devfs.  (Don't ask why, it just does.)
     Naturally, I'm ok moving to udev in 2.6; I had a brief thought
     that perhaps the long devfs pathnames were somehow encoded
     into the persistent superblock of each RAID array, but I
     don't think that's the case - I think the major/minor numbers
     of the disk partitions are stored directly.  (Someone
     correct me if I'm wrong?)

  2) After taking a look at
       http://cgi.cse.unsw.edu.au/~neilb/SoftRaid/01084411399
     I'm not even sure if 2.6 will do autodetection of my 2.4 RAID
     arrays?  Or is this only for RAID arrays created under 2.6?

  3) (related to 2) my 2.4 setup does not uses initrd at all.  The boot
     process basically consists of the boot loader loading the kernel
     and the kernel running /sbin/init.  I rely on the kernel autodetection
     assembling the RAID arrays before init is ever run (as / is on
     /dev/md10).

Any suggestions here?  I'd rather not have to backup filesystems and
start from scratch to get my RAID arrays going.

Thanks,
-Bob

             reply	other threads:[~2004-08-12 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12 15:29 Bob Glamm [this message]
2004-08-12 18:51 ` RAID migration from 2.4 -> 2.6 Bernd Schubert
2004-08-16 22:35 ` Bob Glamm
2004-08-16 22:55   ` Michael Tokarev
2004-08-17  3:23     ` Bob Glamm

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=20040812152939.GD5326@romulus.a-s-i.com \
    --to=glamm@a-s-i.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 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.