[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTil653uFeOct17hj10HbbjBabDPCW6hlAeTQxhxH@mail.gmail.com>
Date: Tue, 1 Jun 2010 16:14:02 -0400
From: Greg Freemyer <greg.freemyer@...il.com>
To: tytso@....edu
Cc: Sunil Mushran <sunil.mushran@...cle.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-ext4@...r.kernel.org,
Joel Becker <Joel.Becker@...cle.com>,
Mark Fasheh <mfasheh@...e.com>
Subject: Re: e4defrag and immutable files
On Tue, Jun 1, 2010 at 3:49 PM, <tytso@....edu> wrote:
> On Tue, Jun 01, 2010 at 12:32:29PM -0700, Sunil Mushran wrote:
>>
>> We (ocfs2) are looking to add a new attribute to denote files that
>> have a fixed allocation on disk. But at the same time, allow writes
>> that do not change the allocation on disk. No truncating, extending,
>> filling holes, etc. We were thinking of calling it "Static" files.
>
> That's an interesting set of semantics, and it might make sense to
> conflate that with a local disk "don't move or defrag" the file
> option. I'm not crazy with the name "static", since it could mean a
> number of other things in other contexts, but I admit I can't think of
> a better name.
FROZEN?
PRE-ALLOCATED?
FALLOCATE_ONLY?
FROZEN_ALLOCATION?
STATIC_ALLOCATION?
I like the last 2 choices myself.
Greg
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists