From: Brian Jackson <brian@brianandsara.net>
To: Igor Krasnoselski <iek@tut.by>, linux-kernel@vger.kernel.org
Subject: Re: Can't mount an ext3 partition - why?
Date: Tue, 17 Jun 2003 10:16:05 -0500 [thread overview]
Message-ID: <200306171016.05828.brian@brianandsara.net> (raw)
In-Reply-To: <11725.030617@tut.by>
devfs will do that, use devfsd to add those legacy device nodes to /dev.
--Brian
On Tuesday 17 June 2003 09:24 am, Igor Krasnoselski wrote:
> Hello Herbert,
>
> HP> what does an fsck.ext3 -fpn on the unmounted filesystem report?
>
> I downloaded 2.4.21 sources, made "make oldconfig" and got a new
> kernel with the same behavior :(
>
> fsck.ext3 (e2fsck 1.27 8-Mar-2002)
> run all 5 passes with no error reports under an old kernel, but under
> new one it says:
>
> fsck.ext3: No such file or directory while trying to open /dev/hdc1
>
> The superblock could not be read....
> etc.
>
> I get further into this, and I find that I have no /dev/hdc1 (and
> /dev/hdc, and /dev/hda too) at all! In place of them(?), I have
>
> /dev/discs/~disc0/disc
> /dev/discs/~disc0/part1
> /dev/discs/~disc0/part2
> /dev/discs/~disc0/part3
> /dev/discs/~disc1/disc
> /dev/discs/~disc1/part1
>
> e2fsck gets them as previous /dev/hd+ args and reports no errors.
> Is this a new feature since 2.4.18-3 kernel? Or maybe this all because
> I add something strange to my config, like "/dev filesystem" ?
--
OpenGFS -- http://opengfs.sourceforge.net
Home -- http://www.brianandsara.net
next prev parent reply other threads:[~2003-06-17 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030617132856.GC24306@www.13thfloor.at>
2003-06-17 14:24 ` Re[2]: Can't mount an ext3 partition - why? Igor Krasnoselski
2003-06-17 15:02 ` Geller Sandor
2003-06-17 15:16 ` Brian Jackson [this message]
2003-06-17 8:15 Igor Krasnoselski
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=200306171016.05828.brian@brianandsara.net \
--to=brian@brianandsara.net \
--cc=iek@tut.by \
--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