Date: 25 Feb 2005 09:00:12 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: "T.F. Cheng" <tfcheng@yahoo.com>, FreeBSD <freebsd-questions@freebsd.org>, Piter <pietro.cerutti@gmail.com> Subject: Re: Directory not empty Message-ID: <44mztsvixf.fsf@be-well.ilk.org> In-Reply-To: <20050225135021.GB18789@alzatex.com> References: <20050225032032.GE60363@dan.emsphone.com> <20050225032917.26920.qmail@web51010.mail.yahoo.com> <20050225135021.GB18789@alzatex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Loren M. Lang" <lorenl@alzatex.com> writes: > On Fri, Feb 25, 2005 at 11:29:17AM +0800, T.F. Cheng wrote: > > man, you are right, I now recall there was a crash > > during the last portupgrade. And there is " > > /dev/ad0s1f: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN > > fsck MANUALLY." in my /var/log. > > Guess the mystery is solved. > > Then why do I have to reboot first then run bgfsck? > > Can I run this myself without rebooting? > > kill -TERM 1 will send your system into single user mode without > rebooting. Assuming you haven't done system like increase the > securelevel, you should be able to fsck the drive from here. The disk will still be mounted read-write. It would be good to umount(8) it before using fsck(8) on it. Then, mounting it again before returning to multi-user mode will be necessary.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44mztsvixf.fsf>