Re: 2.6.0-test1 devfs question

[Daniele Venzano <webvenza@libero.it>]

On Sun, Jul 27, 2003 at 02:30:01AM +0400, Andrey Borzenkov wrote:
> it is hard to tell with the amount of information provided in bug report (even 
> error message is not given). We have three cases here:
> 
> root=123456 (real major/minor number) or root=/dev/md2 (literal string). In 
> both cases init/do_mount_devfs.c:create_dev() should notice that neither 
> /dev/123456 nor /dev/md2 exist, search /dev for ROOT_DEV and create link from 
> /dev/root to real device. If it does not work somethig is broken here, people 
> who can reproduce it should add printk's to create_dev and find_in_devfs to 
> see what happens. It may fail for /dev/md2 if block device name in sysfs 
> differs from "md2" because then it won't find correct ROOT_DEV
> 
> root=/dev/md/2 (literal string) should work simply because /dev/root is linked 
> directly to /dev/md/2
> 
> I do not have any raid devices nor possibility to create them so I cannot 
> test.

Andrew's patch makes it work, the system boots fine with raid and devfs
mounted automatically.
Also using root=/dev/md/2 as boot option works (just tried).

Before the patch I tried with root=/dev/md2, that is what I'm using with
2.4, but didn't work. The error message is:
VFS: cannot open root device "md2" or md2
please append a correct "root=" boot option
Kernel panic: VFS: unable to mount root fs on md2

Let me know if you need more info, but I think the sysfs
explanation is right.

Bye.


-- 
----------------------------------------
Daniele Venzano
Web: http://digilander.iol.it/webvenza/