From: Anders Eriksson <aer-list@mailandnews.com>
To: linux-kernel@vger.kernel.org
Subject: romfs as initrd
Date: Thu, 30 Nov 2000 09:22:45 +0100 [thread overview]
Message-ID: <200011300822.JAA11351@hell.wii.ericsson.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
Running 2.4.0-test10 I try to get an romfs image to work as an initrd
image. It does work when mount `normally` using `mount -o loop`.
However, when used as initrd image it fails. Here's the relevant part
of dmesg:
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: enabling 64 loop devices
RAMDISK: romfs filesystem found at block 0
RAMDISK: Loading 3183 blocks [1 disk]
into ram disk... done. Freeing initrd
memory: 3184k freed
...
devfs: v0.102 (20000622) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Trying fs: ext2
Trying fs: cramfs
wrong magic
Trying fs: romfs
ROMFS DEBUG: rsb_word0 0 rsb_word1 0 sz 0
Kernel panic: VFS: Unable to mount root fs on 01:00
Where the ROMFS DEBUG message comes for this section of romfs/inode.c:
----------------
if (rsb->word0 != ROMSB_WORD0 || rsb->word1 != ROMSB_WORD1
|| sz < ROMFH_SIZE) {
if (!silent)
printk ("VFS: Can't find a romfs filesystem on
dev "
"%s.\n", kdevname(dev));
printk ("ROMFS DEBUG: rsb_word0 %i rsb_word1 %i sz
%i\n",rsb->word0,rsb->word1,sz);
goto out;
----------------
Not knowing that much about fs (and VFS) internals it seems that the
image is identified by the initrd code, but currupted/misplaced so it
cannot be used by the VFS when trying to mount it. I have no ideas what
steps are supposed to happen in between these two.
Help and insights appreciated.
/Anders
[-- Attachment #2: Type: application/pgp-signature, Size: 235 bytes --]
reply other threads:[~2000-11-30 8:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200011300822.JAA11351@hell.wii.ericsson.net \
--to=aer-list@mailandnews.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox