Re: Re[2]: fsck root fs: fsck, devfs, /proc/mounts miscooperate.

Richard Gooch (rgooch@ras.ucalgary.ca)
Wed, 29 Aug 2001 08:27:19 -0600


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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/