Date: Thu, 26 Oct 2000 10:05:04 -0400 From: John <papalia@udel.edu> To: Alfred Perlstein <bright@wintelcom.net> Cc: Salvo Bartolotta <bartequi@inwind.it>, freebsd-questions@FreeBSD.ORG Subject: Re: FSCK & "No write access" Message-ID: <4.3.2.7.2.20001026100228.00aea720@mail.udel.edu> In-Reply-To: <20001025162142.E28123@fw.wintelcom.net> References: <4.3.2.7.2.20001025183208.00ae86c0@mail.udel.edu> <4.3.2.7.2.20001025171553.00ae5880@mail.udel.edu> <4.3.2.7.2.20001025171553.00ae5880@mail.udel.edu> <20001025.22394400@bartequi.ottodomain.org> <4.3.2.7.2.20001025183208.00ae86c0@mail.udel.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > If I try to run fsck without any switches, I still get a read-only
> > >message:
> > >
> > > > merlin# fsck /usr
> > > > ** /dev/da0g (NO WRITE)
> > > > (etc).
> > >
> > >
> > ><dumb question>
> > >
> > >Surely you have done this upon your **unmounted** filesystems (eg
> > >right after booting in single user mode)?
> > >
> > ></dumb question>
> >
> > No suck luck. I'm up-and-running in 'multi-user mode'. In each of the
> > existing FS's (/, /usr, /home, /cvs, and /var) I am fully able to 'cp',
> > 'mv', and 'touch' files. I can also use vi in any of those directories as
> > well to create new files.
>
>Don't run fsck on a mounted filesystem.
Oooooooooops. I misunderstood the 'dumb question'. I feel kinda silly
:) There's a part of the man page which I misinterpreted ("Only partitions
in fstab that are mounted ``rw,'' ``rq'' or ``ro'' and that have non-zero
pass number are checked."). I assumed it could handle mounted & running
systems.
Thank you for setting me straight. :)
--John
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20001026100228.00aea720>