Re: [PATCH 09/13] drop objects larger than --blob-limit if specified

From: Nicolas Pitre <nico@cam.org>
Date: Apr 6, 2007, 20:12 UTC
Message-ID: <alpine.LFD.0.98.0704061604160.28181@xanadu.home>
In-Reply-To: <56b7f5510704061109n2878a221p391b7c3edba89c63@mail.gmail.com>

On Fri, 6 Apr 2007, Dana How wrote:

Show 5 quoted lines

> * Avoiding (e.g.) 2GB+ files when none already exist in the repository --
>  either the filesystem doesn't support anything beyond the limit,
>  or we don't want to use a >31b off_t with mmap.  (Perhaps
>  the latter case is completely avoided by some glibc 64b trickery,
>  but is that always true?)  Only the write rollback approach can address this.

If the filesystem doesn't support anything beyond the limit, you cannot perform any rollback either. Because if you roll back that's because you crossed the limit already. But you're not supposed to even be able to cross that limit in the first place if the filesystem is limited.

Nicolas