+ char *device_names[MAX_MD_DEVS];
} md_setup_args md__initdata;
/*
@@ -3659,25 +3660,24 @@
* md=n,device-list reads a RAID superblock from the devices
* elements in device-list are read by name_to_kdev_t so can be
* a hex number or something like /dev/hda1 /de
linux-2.4.1p11-1/drivers/md/md.c
line 3643
-#define MAX_MD_BOOT_DEVS 8
+#define MAX_MD_BOOT_DEVS MAX_MD_DEVS
---
To: Dave Cinege <[EMAIL PROTECTED]>
On Mon, 29 Jan 2001, Dave Cinege wrote:
> -#define MAX_MD_BOOT_DEVS 8
&
Douglas Gilbert wrote:
>
> Dave,
> Look at the dmesg output and check that your
> "Kernel command line:" is what you think it
> is. Some older versions of lilo truncate it.
> Here is mine (which is what I expected):
>
> Kernel command line: auto BOOT_IMAGE=lin240 ro root=803 scsihosts=imm:advans
Sandy Harris wrote:
> Looks to me like this parsing code unnecessarily and rather clumsily
> re-invents strtok
The original parsing code is this:
if ((str = strchr(str, ',')) != NULL)
str++;
Which effectivly steps through
/dev/sda1,/dev/sda
I have multiple Linux hosts on a SAN, making autodetect of raid devices
dangerous. This problem should be solved by specing an 'md=' for each device on
the cmdline, but unfortuantly it's broken.
Between a few emails to mingo and several wasted hours, I've managed to figure
out the problem. Howeve
5 matches
Mail list logo
