Date: Fri, 25 Feb 2005 05:50:21 -0800 From: "Loren M. Lang" <lorenl@alzatex.com> To: "T.F. Cheng" <tfcheng@yahoo.com> Cc: Piter <pietro.cerutti@gmail.com> Subject: Re: Directory not empty Message-ID: <20050225135021.GB18789@alzatex.com> In-Reply-To: <20050225032917.26920.qmail@web51010.mail.yahoo.com> References: <20050225032032.GE60363@dan.emsphone.com> <20050225032917.26920.qmail@web51010.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. I believe just typing exit will go back for multi-user mode. > > thanks! > > > > --- Dan Nelson <dnelson@allantgroup.com> ?g?D?G > > In the last episode (Feb 25), T.F. Cheng said: > > > yeah, it's weird. I found that I can rename it (to > > tmp) then I tried > > > to del it: > > > > rm -fr tmp > > > rm: tmp/qt-x11-free-3.3.4/doc: Directory not empty > > > rm: tmp/qt-x11-free-3.3.4/src: Directory not empty > > > > Do you use softupdates, and did your system happen > > to crash after a > > portupgrade? I bet if you cd into > > tmp/qt-x11-free-3.3.4/doc and run ls > > -la, you'll see something like: > > > > $ ls -la > > total 2 > > drwx------ 4 dan dan 512 Feb 22 11:00 ./ > > drwxr-xr-x 3 dan dan 512 Feb 22 11:00 ../ > > > > The "." entry should have 2 links in an empty > > directory (one here, and > > one in the parent directory). That's caused be a > > failed background > > fsck, which is supposed to reset bad link counts > > after a crash. If you > > check /var/log/messages, you might see something > > like this: > > > > PARTIALLY TRUNCATED INODE I=316179 > > UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck > > MANUALLY. > > > > Try rebooting and letting the bgfsck run again, or > > boot into > > single-user mode and run fsck -p on the filesystem. > > > > -- > > Dan Nelson > > dnelson@allantgroup.com > > > > ===== > Best Regards, > > Tsu-Fan Cheng > > _________________________________________________________ > Do You Yahoo!? > ?n?O?K?O?? @yahoo.com ?????q?l?l?? @ http://chinese.mail.yahoo.com > Get your free @yahoo.com address at http://chinese.mail.yahoo.com > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050225135021.GB18789>