Date: Wed, 25 Oct 2000 16:21:42 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: John <papalia@udel.edu> Cc: Salvo Bartolotta <bartequi@inwind.it>, freebsd-questions@FreeBSD.ORG Subject: Re: FSCK & "No write access" Message-ID: <20001025162142.E28123@fw.wintelcom.net> In-Reply-To: <4.3.2.7.2.20001025183208.00ae86c0@mail.udel.edu>; from papalia@udel.edu on Wed, Oct 25, 2000 at 06:38:30PM -0400 References: <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
* John <papalia@udel.edu> [001025 15:40] wrote: > At 10:39 PM 10/25/2000 +0000, Salvo Bartolotta wrote: > > > > > 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. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." 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?20001025162142.E28123>