Subject: Re: fsck issue
To: Charles M. Hannum <mycroft@mit.edu>
From: Michael L. VanLoon -- HeadCandy.com <michaelv@HeadCandy.com>
List: current-users
Date: 08/05/1996 21:30:04
>Markus Illenseer <markus@server.peacock.de> writes:
>>  Just a question which is bothering me for a while already.
>> I want to perform a fsck on my hard drives w/o beeing forced to
>> umount the partitions. 
>>  Is it possible to temporarily lock the drives and then start fsck 
>> beeing able to write fixes?

>If you're running with securelevel > 0, you won't be able to write to
>a mounted partition.  If not, you could `mount -u -r' it to downgrade
>the mount to read-only while you run fsck(8), and then do a `mount -u
>-o reload' when you're done.  (I'm not actually sure whether the `-o
>reload' is necessary there, but it wouldn't hurt.)

Of course, the problem with that being that a process that tries to
write to that filesystem during that period of time will get an error,
instead of just blocking until the check is done, which would be the
desired behavior.

-----------------------------------------------------------------------------
  Michael L. VanLoon                                 michaelv@HeadCandy.com
        --<  Free your mind and your machine -- NetBSD free un*x  >--
    NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3,
        Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32...
    NetBSD ports in progress: PICA, others...

   Roll your own Internet access -- Seattle People's Internet cooperative.
                  If you're in the Seattle area, ask me how.
-----------------------------------------------------------------------------