Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: ext3 and undeletion | Date | 26 Feb 2002 08:55:17 -0800 |
| |
Followup to: <20020226164036.GG4393@matchmail.com> By author: Mike Fedyk <mfedyk@matchmail.com> In newsgroup: linux.dev.kernel > > Uhh, no. > > You have a configurable size for the undelete dirs and you delete a file. > Now, that file gets moved to $mountpoint/.undelete. The daemon gets > notified through a socket, and it can check to see if it needs to delete any > older deleted files to make sure .undelete doesn't get bigger than > configured. > > We're only scanning the dirs upon daemon startup (reminds me of > quota... ;), and all other daemon actions are triggered by unlink() writing > to a socket. The worst thing that can happen is not seeing your free space > immediately, but a few seconds later. >
Hence race condition. Also, the solution to hard-reserve space seems to fundamentally defeat the purpose (IMO).
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |