Ask a Question related to FreeBSD, Design and Development.

  1. #1

    Default 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 中文電子郵件 @ [url]http://chinese.mail.yahoo.com[/url]
    Get your free @yahoo.com address at [url]http://chinese.mail.yahoo.com[/url]
    T.F. Cheng Guest

  2. Similar Questions and Discussions

    1. Why do I have 20,000 empty Acr*.TMP files on my system root directory?
      I have about 20,000 empty .TMP files on my C:\ root directory that begin with "Acr", leading me to believe they were caused by Acrobat. Anyone know...
    2. #25885 [Opn->Csd]: mail() causes apache2 to crash when message is empty, and headers is non-empty
      ID: 25885 Updated by: sniper@php.net Reported By: ben at krackeler dot com -Status: Open +Status: ...
    3. #25885 [NEW]: mail() causes apache2 to crash when message is empty, and headers is non-empty
      From: ben at krackeler dot com Operating system: WinXP PHP version: 4.3.3 PHP Bug Type: Mail related Bug description: ...
    4. Not able to erase an empty directory... ?
      Hi, all: I have a really weird behaviour in my Debian box. I wanted to clean out today the wine installation that I have removing all the...
    5. 'Non-empty' directory deletion.
      Hi, I'm trying to delete /home/adam/.enlightenment/themes/FossilsOfTheMachines but I can't get 'rmdir' to work on a full directory. Neither ...
  3. #2

    Default 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 <tfcheng@yahoo.com> 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 銝*餃*萎辣 @ [url]http://chinese.mail.yahoo.com[/url]
    > Get your free @yahoo.com address at [url]http://chinese.mail.yahoo.com[/url]
    > _______________________________________________
    > [email]freebsd-questions@freebsd.org[/email] mailing list
    > [url]http://lists.freebsd.org/mailman/listinfo/freebsd-questions[/url]
    > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    >

    --
    Pietro "Piter" Cerutti
    <pietro.cerutti@gmail.com>
    <piter@beansidhe.ch>

    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?"
    Piter Guest

  4. #3

    Default 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 <pietro.cerutti@gmail.com> 寫道:
    > 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
    > <tfcheng@yahoo.com> 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 中文電子郵件 @
    > [url]http://chinese.mail.yahoo.com[/url]
    > > Get your free @yahoo.com address at
    > [url]http://chinese.mail.yahoo.com[/url]
    > > _______________________________________________
    > > [email]freebsd-questions@freebsd.org[/email] mailing list
    > >
    >
    [url]http://lists.freebsd.org/mailman/listinfo/freebsd-questions[/url]
    > > To unsubscribe, send any mail to
    > "freebsd-questions-unsubscribe@freebsd.org"
    > >
    >
    >
    > --
    > Pietro "Piter" Cerutti
    > <pietro.cerutti@gmail.com>
    > <piter@beansidhe.ch>
    >
    > 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 中文電子郵件 @ [url]http://chinese.mail.yahoo.com[/url]
    Get your free @yahoo.com address at [url]http://chinese.mail.yahoo.com[/url]
    T.F. Cheng Guest

  5. #4

    Default 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]dnelson@allantgroup.com[/email]
    Dan Nelson Guest

  6. #5

    Default 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 <dnelson@allantgroup.com> 寫道:
    > 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]dnelson@allantgroup.com[/email]
    >
    =====
    Best Regards,

    Tsu-Fan Cheng

    __________________________________________________ _______
    Do You Yahoo!?
    登記免費的 @yahoo.com 中文電子郵件 @ [url]http://chinese.mail.yahoo.com[/url]
    Get your free @yahoo.com address at [url]http://chinese.mail.yahoo.com[/url]
    T.F. Cheng Guest

  7. #6

    Default 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]dnelson@allantgroup.com[/email]
    Dan Nelson Guest

  8. #7

    Default 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 <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
    > > [email]dnelson@allantgroup.com[/email]
    > >
    >
    > =====
    > Best Regards,
    >
    > Tsu-Fan Cheng
    >
    > __________________________________________________ _______
    > Do You Yahoo!?
    > ?n?O?K?O?? @yahoo.com ?????q?l?l?? @ [url]http://chinese.mail.yahoo.com[/url]
    > Get your free @yahoo.com address at [url]http://chinese.mail.yahoo.com[/url]
    > _______________________________________________
    > [email]freebsd-questions@freebsd.org[/email] mailing list
    > [url]http://lists.freebsd.org/mailman/listinfo/freebsd-questions[/url]
    > 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: [url]ftp://ftp.tallye.com/pub/lorenl_pubkey.asc[/url]
    Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C

    Loren M. Lang Guest

  9. #8

    Default Re: Directory not empty

    "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.
    Lowell Gilbert Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139