[lkml]   [2002]   [Jan]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [reiserfs-list] Boot failure: msdos pushes in front of reiserfs

    On Mon, Jan 14, 2002 at 03:00:21PM +0100, Matthias Andree wrote:

    > > > 4. I asked Ewald to boot with rootfstype=reiserfs, but he reported that
    > > > this did not help, news:<a1sb7b$t2d2e$>
    > > > (German-language).
    > > Hm, probably because reiserfs is not in kernel, but is an external module.
    > Yes, but this module is loaded from SuSE's initrd, so it is loaded
    > before the root file system is mounted. Might it be that "rootfstype" is
    > already checked as the initrd is mounted rather then when the actual
    > root is mounted? If so, fs/super.c deserves fixing, but I'm not
    > acquainted with that code, so I cannot tell or fix that now.
    Looking at init/main.c and fs/super.c,
    rootfsflags parameter is never saved, moreover - it's original value is destroyed, once initrd fs is mounted.
    And I only see not very nice ways of fixing this, so perhaps someone more exeprienced can come up with the solution?
    (my crappy ides is not to do putname() on fs_names, if (real_root_dev != ROOT_DEV), all of this is only when CONFIG_..._INITRD

    > > > 2. mkreiserfs could also zero out so much of old data on the FS so that
    > > > the kernel reliably recognizes the FS as reiserfs and fails to mount
    > > > that stuff as msdos
    > > External tools (lilo and stuff) can live there, this will destroy them.
    > >
    > > Correct solution, if you create filesystem with mkreiserfs, and you
    > > have no reliable way to pass fstype to kernel, when this partition is mounted
    > > should be to destroy all occurences of other fs's superblocks by yourself, obviously.
    > Sure, but tell newbies how to do that. (Tell distributors first. :-)
    Our internal deecision is now to detect if device, we are going to mkfs have FAT superblock,
    and if it is, zero it out.

    > > > 3. Distributors, when making their initrd stuff, should make sure that
    > > > all Linux-native file systems are tried first.
    > > FS tryout order is hard-wired into the kernel (and depends on linking order, AFAIK).
    > Yup, reiserfs is last in /proc/filesystems when loaded as module, but on
    > my private machine (where it's linked into the kernel), it's right after
    > ext2 and before vfat.
    Do you have vfat as a loadable module?

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:15    [W:0.022 / U:25.728 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site