Re: freebsd-update 7.0-7.4 problem: rmdir Directory not empty
On Fri, Jun 03, 2011 at 10:21:13AM -0400, Brent Bloxam wrote: I'm going through the freebsd-update process to move from 7.0 to 7.4. I followed the handbook, rebooted to GENERIC and followed up with `freebsd-update install` and got the following output: # freebsd-update install Installing updates...rmdir: ///usr/share/man/ja: Directory not empty rmdir: ///usr/share/man/en.ISO8859-1/cat8: Directory not empty rmdir: ///usr/share/man/en.ISO8859-1/cat4: Directory not empty rmdir: ///usr/share/man/cat8: Directory not empty rmdir: ///usr/share/man/cat4: Directory not empty done. Are these rmdir lines something to be concerned about? Should I remove them and their content? I wouldn't worry too much about that. I've still got those dirs on my 7.3 machine. The worst case scenario, I think, is that you may have some old manpages lying around. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpPagg6ub9fe.pgp Description: PGP signature
freebsd-update 7.0-7.4 problem: rmdir Directory not empty
I'm going through the freebsd-update process to move from 7.0 to 7.4. I followed the handbook, rebooted to GENERIC and followed up with `freebsd-update install` and got the following output: # freebsd-update install Installing updates...rmdir: ///usr/share/man/ja: Directory not empty rmdir: ///usr/share/man/en.ISO8859-1/cat8: Directory not empty rmdir: ///usr/share/man/en.ISO8859-1/cat4: Directory not empty rmdir: ///usr/share/man/cat8: Directory not empty rmdir: ///usr/share/man/cat4: Directory not empty done. Are these rmdir lines something to be concerned about? Should I remove them and their content? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Directory not empty
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 [EMAIL PROTECTED] ?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 [EMAIL PROTECTED] = 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 [EMAIL PROTECTED] -- 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Directory not empty
Loren M. Lang [EMAIL PROTECTED] 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Directory not empty
I swear I have googled it and checked out the mailing list already and still I cannot remove this directory. It's qt33's work under ports and I need to upgrade my qt33 port. I am root and have tried rm -fr work/ chflags noschg work/ then rm -fr. Still it said Directory not empty. What's the deal? TFC = Best Regards, Tsu-Fan Cheng _ Do You Yahoo!? @yahoo.com @ 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 [EMAIL PROTECTED]
Re: Directory not empty
It's a strange thing. Try rm -rfv work/ with verbose on maybe you'll figure out what file gives the problem... then just try to delete it or rename it... Really can't see what the problem should be... On Fri, 25 Feb 2005 08:26:44 +0800 (CST), T.F. Cheng [EMAIL PROTECTED] wrote: I swear I have googled it and checked out the mailing list already and still I cannot remove this directory. It's qt33's work under ports and I need to upgrade my qt33 port. I am root and have tried rm -fr work/ chflags noschg work/ then rm -fr. Still it said Directory not empty. What's the deal? TFC = Best Regards, Tsu-Fan Cheng _ Do You Yahoo!? @yahoo.com @ 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 [EMAIL PROTECTED] -- Pietro Piter Cerutti [EMAIL PROTECTED] [EMAIL PROTECTED] Beansidhe - SwiSS Death / Thrash Metal www.beansidhe.ch Windows: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Directory not empty
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 rm: tmp/qt-x11-free-3.3.4/tools/qvfb: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/makeqpf: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/assistant: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/mergetr: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/qtconfig: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/msg2qm: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/qembed: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/designer: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/linguist/book: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/linguist/qm2ts: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/linguist/lrelease: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/linguist/lupdate: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools/linguist: Directory not empty rm: tmp/qt-x11-free-3.3.4/tools: Directory not empty rm: tmp/qt-x11-free-3.3.4: Directory not empty rm: tmp/: Directory not empty Oh! my god TFC --- Piter [EMAIL PROTECTED] It's a strange thing. Try rm -rfv work/ with verbose on maybe you'll figure out what file gives the problem... then just try to delete it or rename it... Really can't see what the problem should be... On Fri, 25 Feb 2005 08:26:44 +0800 (CST), T.F. Cheng [EMAIL PROTECTED] wrote: I swear I have googled it and checked out the mailing list already and still I cannot remove this directory. It's qt33's work under ports and I need to upgrade my qt33 port. I am root and have tried rm -fr work/ chflags noschg work/ then rm -fr. Still it said Directory not empty. What's the deal? TFC = Best Regards, Tsu-Fan Cheng _ Do You Yahoo!? @yahoo.com @ 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 [EMAIL PROTECTED] -- Pietro Piter Cerutti [EMAIL PROTECTED] [EMAIL PROTECTED] Beansidhe - SwiSS Death / Thrash Metal www.beansidhe.ch Windows: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? = Best Regards, Tsu-Fan Cheng _ Do You Yahoo!? @yahoo.com @ 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 [EMAIL PROTECTED]
Re: Directory not empty
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 [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Directory not empty
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? thanks! --- Dan Nelson [EMAIL PROTECTED] 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 [EMAIL PROTECTED] = Best Regards, Tsu-Fan Cheng _ Do You Yahoo!? @yahoo.com @ 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 [EMAIL PROTECTED]
Re: Directory not empty
In the last episode (Feb 25), T.F. Cheng said: 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? Actually running a 2nd bgfsck probably won't work, since it'll just hit the same problem. A regular fsck has to be run on a dismounted volume, and booting single-user is the easiest way of doing that. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
