public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: torvalds@transmeta.com, Andries.Brouwer@cwi.nl,
	Peter Samuelson <peter@cadcamlab.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch-2.4.0-test13-pre3] rootfs (2nd attempt)
Date: Mon, 18 Dec 2000 11:23:27 -0700 (MST)	[thread overview]
Message-ID: <200012181823.eBIINRo28087@webber.adilger.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0012181547500.830-100000@penguin.homenet> "from Tigran Aivazian at Dec 18, 2000 04:00:45 pm"

Tigran, you write:
> Thanks to suggestions from Andries and Peter I enhanced the rootfs patch
> to do the same it did before + panic when rootfs= is given but failed to

If I could add one thing here (we have had a 2.2 patch like this for testing
with ext3) - if you specify the rootfstype parameter don't use the "quiet"
option to read_super, so you know why it couldn't mount a specific filesystem
as root, and/or print rootfs type in the panic message.

This is especially useful if you have something in LILO that you forgot about...

Cheers, Andreas
=============================================================================
diff -urN -X dontdiff linux/fs/super.c rootfs/fs/super.c
--- linux/fs/super.c	Tue Dec 12 09:25:22 2000
+++ rootfs/fs/super.c	Mon Dec 18 14:49:08 2000
@@ -1600,7 +1600,7 @@
 	if (*rootfs) {
 		fs_type = get_fs_type(rootfs);
 		if (fs_type) {
-  			sb = read_super(ROOT_DEV,bdev,fs_type,root_mountflags,NULL,1);
+  			sb = read_super(ROOT_DEV,bdev,fs_type,root_mountflags,NULL,0);
 			if (sb)
 				goto mount_it;
 		} 
@@ -1622,7 +1622,8 @@
 	}
 	read_unlock(&file_systems_lock);
 fail:
-	panic("VFS: Unable to mount root fs on %s", kdevname(ROOT_DEV));
+	panic("VFS: Unable to mount root %s on %s", *rootfs ? rootfs : "fs",
+	      kdevname(ROOT_DEV));
 
 mount_it:
 	printk ("VFS: Mounted root (%s filesystem)%s.\n",

-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-18 18:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-18 14:17 [patch-2.4.0-test13-pre3] rootfs boot param. support Andries.Brouwer
2000-12-18 15:22 ` Peter Samuelson
2000-12-18 15:36   ` Tigran Aivazian
2000-12-18 16:00   ` [patch-2.4.0-test13-pre3] rootfs (2nd attempt) Tigran Aivazian
2000-12-18 16:03     ` Oops " Tigran Aivazian
2000-12-18 18:23     ` Andreas Dilger [this message]
2000-12-18 18:31       ` [final] " Tigran Aivazian
2000-12-19  7:03         ` Is there a devfs patch for 2.2.18? Tri D. Hoang

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=200012181823.eBIINRo28087@webber.adilger.net \
    --to=adilger@turbolinux.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@cadcamlab.org \
    --cc=tigran@veritas.com \
    --cc=torvalds@transmeta.com \
    /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