From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
Cc: Andreas Dilger <adilger@turbolabs.com>, linux-kernel@vger.kernel.org
Subject: Re: Re[2]: fsck root fs: fsck, devfs, /proc/mounts miscooperate.
Date: Wed, 29 Aug 2001 08:27:19 -0600 [thread overview]
Message-ID: <200108291427.f7TERJj07458@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <6410958637.20010829151417@port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: <22075604.20010829095413@port.imtp.ilyichevsk.odessa.ua> <20010829021304.D24270@turbolinux.com> <6410958637.20010829151417@port.imtp.ilyichevsk.odessa.ua>
VDA@port.imtp.ilyichevsk.odessa.ua writes:
> Hello Andreas,
>
> Wednesday, August 29, 2001, 11:13:04 AM, you wrote:
> >> # fsck /dev/scsi/host0/bus0/target1/lun0/part1
> >> Parallelizing fsck version 1.15 (18-Jul-1999)
> >> e2fsck 1.15, 18-Jul-1999 for EXT2 FS 0.5b, 95/08/09
> >> /dev/scsi/host0/bus0/target1/lun0/part1 is mounted.
> >>
> >> WARNING!!! Running e2fsck on a mounted filesystem may cause
> >> SEVERE filesystem damage...
>
> AD> Get a new version of e2fsprogs (at http://sf.net/projects/e2fsprogs).
> AD> The detection of mounted root filesystems has changed in recent releases,
> AD> so it _should_ be fixed - let us know if it is not.
>
> Installed e2fsprogs 1.23. It does not print warning now on
> "fsck /dev/scsi/host0/bus0/target1/lun0/part1"
> However, it still cannot fs check root fs when given "fsck /" which I
> really need in my init script. Now the only way to do root fs check
> for me is to parse /proc/mounts and extract mount point for / via sed
> (I have never used sed yet...).
>
> # 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 /
>
> The superblock could not be read or does not describe a correct ext2
> filesystem...
You say you are running devfs. Well, if that's the case, you can
simply do:
# fsck /dev/root
because devfs makes /dev/root a symbolic link to the root FS device.
Magic.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-08-29 14:27 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 ` Richard Gooch [this message]
2001-08-29 12:14 ` Re[2]: " 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 ` Re[4]: " VDA
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=200108291427.f7TERJj07458@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--cc=adilger@turbolabs.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;
as well as URLs for NNTP newsgroup(s).