Re: Ext3 as root filesystem?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 06 December 2003 13:32, Leonard den Ottolander wrote:

Hi Leonard -

Thanks for your reply :-)

>  I don't think the second stage will use the modules from the initrd.
>
> Are you sure it is available under
> /lib/modules/<version>/kernel/fs/? You might want to run depmod -a,
> although that should be called by the init scripts as well.

I confess in the initrd I had copied them into /lib "to make things simple".  
After your email I improved this to keep the same /lib/modules/<ver>/... 
structure in the initrd, and I ran depmod with -a -b <fake root> on both the 
initrd and the root filesystem at generation time, and the modules are now to 
be found in the same place in the main root filesystem and the initrd.  
(Depmod is done in /etc/rc.sysinit but not until after the fsck that is 
blowing up).

In the meanwhile while trying things in /etc/fstab I managed to get the 
/etc/rc.sysinit to fail to do the fsck properly, this means that the error is 
skipped temporarily, and I find to my delight I do get through to a login 
prompt and then into bash.  So I am close.

Unfortunately even with the depmods and the improved directory structure for 
the modules in the initrd, the kernel still insists on pulling in the ext3 
root fs as ext2.  The messages I am seeing just before init starts up are

EXT2-fs warning (device nbd(43,0)): ext2_read_super: mounting ext3 filesystem 
as ext2
VFS: Mounted root (ext2 filesystem)
Trying to move the old root into /initrd ... okay
Freeing unused kernel memory: 120k freed

Having ext3 is important, because the root filesystem is on another machine 
using the Network Block Device, it can be expected to experience rough 
treatment.

>  The module should be loaded on demand. 

What prompts the kernel to try to load the ext3 modules?  If I try 
rootfstype=ext3 the kernel seems to understand this to mean that the initrd 
is ext3 (it is in fact ext2 since that's how the Fedora one is formatted).

Since this is all based on the Fedora initrd, I must be missing something or 
doing something (else) stupid, because Fedora has no trouble coming up on 
ext3 on my laptop HDD here :-(

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/0ebHjKeDCxMJCTIRAgruAJ4j5nwpM3Z80qWCTXQmvN0jLlxqmwCfYrG4
92PSM2MN48SBrm5KfcjTQtQ=
=CRDR
-----END PGP SIGNATURE-----




[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux