From: Prasanna P Subash <psubash@turbolinux.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: ext2 superblock issue on 2.4.1-ac20
Date: Wed, 21 Feb 2001 18:32:36 -0800 [thread overview]
Message-ID: <20010221183236.A396@turbolinux.com> (raw)
In-Reply-To: <20010221163514.A671@turbolinux.com> <E14VjyB-000391-00@the-village.bc.nu>
In-Reply-To: <E14VjyB-000391-00@the-village.bc.nu>; from Alan Cox on Thu, Feb 22, 2001 at 12:50:52AM +0000
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
oops. sorry for the panic. my fault.
I was trying to boot a non-devfs'ed with devfs.
thanks anyway.
--
Prasanna Subash --- psubash@turbolinux.com --- TurboLinux, INC
------------------------------------------------------------------------
Linux, the choice | Who is John Galt?
of a GNU generation -o) |
Kernel 2.4.1-ac20 /\\ |
on a i686 _\\_v |
|
------------------------------------------------------------------------
On Thu, Feb 22, 2001 at 12:50:52AM +0000, Alan Cox wrote:
> > I just oldconfiged linux kernel with my 2.4.1 .config. When I boot the new
> > 2.4.1-ac20 kernel, I get a message saying that my ext2 superblock is corrup=
> > ted.
> > I get a message asking me to run e2fsck -b 8193 <...hdd dev..>
> > My 2.4.0-ac4 that I've been running for more than 2-3 weeks now has no prob=
> > lems
> > booting though.
> >
> > What am I doing wrong ? I would be glad to give more info.
>
> Sounds like a driver change broke the handling for your disks or re-ordered
> them.
>
> What hardware
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-02-22 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 0:35 PROBLEM: ext2 superblock issue on 2.4.1-ac20 Prasanna P Subash
2001-02-22 0:50 ` Alan Cox
2001-02-22 1:16 ` Prasanna P Subash
2001-02-22 2:32 ` Prasanna P Subash [this message]
2001-02-22 0:51 ` Andreas Dilger
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=20010221183236.A396@turbolinux.com \
--to=psubash@turbolinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.