Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!umich!umeecs!msi-s0.msi.umn.edu!cs.umn.edu!bungia!cimcor!det
From: det@cimcor.mn.org (Derek Terveer)
Newsgroups: comp.unix.questions
Subject: Re: Recurring problem in root filesystem
Message-ID: <1990Sep4.181938.8080@cimcor.mn.org>
Date: 4 Sep 90 18:19:38 GMT
Organization: Scandia Microsystems
Lines: 25

In article <15590:Sep402:41:0190@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> In article <4010@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
> > >Try running fsck on the *unmounted* root filesystem,
> > Try unmounting the root filesystem first.  Good luck....
> 
> Wait a minute. Can't you chroot() to another filesystem, then remount
> the original root below the new one? I haven't tested this but it seems
> like it should work on an otherwise unused system.

Wait a minute.  This shouldn't be necessary at all -- at least in
system V.  Bring the system down into single user and then run fsck on
the Block Device for root (not the char device).  For example:

fsck /dev/dsk/0s1

Since one can't unmount root while one is running from it, it makes
sense that one should be able to fsck it while you one is running on
it.  The alternative is to boot from some other media (another disk, a
tape, etc) and *then* run fsck on either the blocked or raw root
partition.

derek
-- 
temporarily:  			derek@cimcor.MN.ORG
as soon as i get my pc back:	det@hawkmoon.MN.ORG