linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@turbolabs.com>, linux-kernel@vger.kernel.org
Subject: Re[4]: fsck root fs: fsck, devfs, /proc/mounts miscooperate.
Date: Fri, 31 Aug 2001 13:58:42 +0300	[thread overview]
Message-ID: <985431419.20010831135842@port.imtp.ilyichevsk.odessa.ua> (raw)
In-Reply-To: <20010830153910.C3114@thunk.org>
In-Reply-To: <22075604.20010829095413@port.imtp.ilyichevsk.odessa.ua> <20010829021304.D24270@turbolinux.com> <6410958637.20010829151417@port.imtp.ilyichevsk.odessa.ua> <20010830153910.C3114@thunk.org>

Hello Ted,

Thursday, August 30, 2001, 10:39:10 PM, you wrote:
>> # fsck /
>> Parallelizing fsck version 1.15 (18-Jul-1999)
>> e2fsck 1.15, 18-Jul-1999 for EXT2 FS 0.5b, 95/08/09
>> /sbin/e2fsck: Is a directory while trying to open /

TT> Umm... it works for me.  (No, I don't use devfs, but I do test
TT> e2fsprogs to make sure they do some sane vs. devfs by using UML...)
...
TT> What does your /etc/mtab file show for an entry for the root
TT> filesystem when you're trying to make it work?  Fsck does require that
TT> /etc/mtab is sane, and I'm guessing that you're missing an entry in
TT> /etc/mtab for /. 

My /etc/mtab is symlinked to /proc/mounts and have these entries:
/dev/scsi/host0/bus0/target1/lun0/part1 / ext2 ro 0 0
/dev/sda2 /.share ext2 rw 0 0
...

Also fsck does not work for my second mountpoint if specified
as a relative path:

pegasus:/#fsck .share    <--- relative path
Parallelizing fsck version 1.23 (15-Aug-2001)
No devices specified to be checked!
pegasus:/#fsck /.share    <--- absolute path
Parallelizing fsck version 1.23 (15-Aug-2001)
e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
/dev/sda2 is mounted.
WARNING! Running e2fsck on a mounted filesystem...

Looks like running "fsck <mountpoint>" is uncommon
and isn't tested much.
--
Best regards,
VDA
mailto:VDA@port.imtp.ilyichevsk.odessa.ua
http://port.imtp.ilyichevsk.odessa.ua/vda/



      parent reply	other threads:[~2001-08-31 11:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29  6:54 fsck root fs: fsck, devfs, /proc/mounts miscooperate VDA
2001-08-29  8:13 ` Andreas Dilger
2001-08-29 14:27   ` Re[2]: " Richard Gooch
2001-08-29 12:14 ` VDA
2001-08-29 18:17   ` Andreas Dilger
2001-08-29 19:03   ` Richard Gooch
2001-08-29 19:21   ` Re[4]: " VDA
2001-08-30 19:39   ` Re[2]: " Theodore Tso
2001-08-31 10:58   ` VDA [this message]

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=985431419.20010831135842@port.imtp.ilyichevsk.odessa.ua \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=adilger@turbolabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).