Date: Fri, 25 Jan 2002 10:54:51 -0500 From: Bill Moran <wmoran@potentialtech.com> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: fsck Message-ID: <02012510545108.07381@proxy.pt.com> In-Reply-To: <20020125162235.GP87583@dan.emsphone.com> References: <OE9lmLFQG101s7hpJm80001a61d@hotmail.com> <20020125162235.GP87583@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 25 January 2002 11:22, Dan Nelson wrote: > In the last episode (Jan 25), dseeger said: > > when running fsck -p I get "NO write Access" and then "unexpected > > incositancies" > > > > is this because of other processes running - or do i really have a > > permission problem > > You should only run fsck on unmounted volumes, or read-only volumes in > single-user mode. Don't run it after the system has come up. This question seems to come up rather often. Should fsck refuse to start if it's being run on a mounted volume? Possibly with an error like "Please unmount /dev/ad?s1? before running fsck"? Or is there a reason why such behaviour would be undesirable? -- Bill Moran Potential Technology technical services http://www.potentialtech.com 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?02012510545108.07381>