Cannot delete directory after crash

From: Jason DiCioccio (jd_at_ods.org)
Date: 06/30/04

  • Next message: Thyer, Matthew: "RE: cvs-src summary for June 21 - 28"
    Date: Tue, 29 Jun 2004 21:43:28 -0400
    To: freebsd-current@freebsd.org
    
    

    Greetings,
      This is just to report a problem I had recently with FreeBSD 5-CURRENT
    (from a couple of weeks ago) with a full filesystem. The box first froze
    due to an FS being full for an extended period of time (I've seen it happen
    before with 4.x as well). After having the box rebooted, it came back up
    and I started clearing out some space on it. What I did not realize until
    later was that fsck -B was running on that filesystem. This caused rm to
    obviously have no effect since there was an active snapshot of the
    filesystem. Free space remained about the same.

      The main problem I encountered though was that there were some
    directories that i could not delete. rm -rf would constantly return an
    error saying that the directory was not empty. After running fsck -fy on
    it, the problem appears to have gone away. I have a theory on why I think
    this happened though...

      I think that the snapshot code was trying to write data to a filled disk
    (copy on write) while I was deleting a bunch of files and fsck was running.
    This is my theory on why softupdates was unable to do its job properly. I
    can't confirm that, but I think it might be something worth looking into.
    Is the snapshot code smart enough to deal with that situation?

    Let me know if this makes any sense. I am also off list, so please CC me
    in any replies.

    Thanks in advance!
    -JD-
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Thyer, Matthew: "RE: cvs-src summary for June 21 - 28"

    Relevant Pages

    • Re: fsckd - FIXED
      ... filesystem errors on boot, with the "hit control-D to continue or give root ... to fix the errors with fsck. ... filesystem and inability to reboot. ...
      (Debian-User)
    • Re: Ignorant user overfilled /usr; strange errors followed. Fixed with fsck -y, but what exactly
      ... While attempting to follow filesystem activity (and not realising the ... X/KDE, and found a whole sequence of 'filesystem is full' errors on ... Don't run fsck on a live filesystem; ... filesystem that apparently had no free blocks. ...
      (freebsd-questions)
    • Re: Fw: Help:FW Harddisk has no space!
      ... good to hear what you found using fsck. ... reboot the system after the command. ... > Filesystem 1K-blocks Used Avail Capacity ... > tem on which the correction will take place, ...
      (freebsd-questions)
    • 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted
      ... I just tried the 2.6.22-r1 candidate to test whether some bug I have ... schedules on my filesystem after 38 clean mounts. ... The fsck found some unused inodes, ... HTREE directory inode 1163319 has an invalid root node. ...
      (Linux-Kernel)
    • Re: fsckd
      ... filesystem errors on boot, with the "hit control-D to continue or give root ... to fix the errors with fsck. ... filesystem and inability to reboot. ...
      (Debian-User)