From: Eric Sandeen <sandeen@redhat.com>
To: tytso@mit.edu
Cc: Sunil Mushran <sunil.mushran@oracle.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-ext4@vger.kernel.org, Joel Becker <Joel.Becker@oracle.com>,
Mark Fasheh <mfasheh@suse.com>
Subject: Re: e4defrag and immutable files
Date: Tue, 01 Jun 2010 16:00:15 -0500 [thread overview]
Message-ID: <4C0574DF.3030303@redhat.com> (raw)
In-Reply-To: <20100601194924.GF4426@thunk.org>
tytso@mit.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.
>
> - Ted
fixed-mapping files maybe?
-Eric
next prev parent reply other threads:[~2010-06-01 21:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 20:14 e4defrag and immutable files H. Peter Anvin
2010-05-28 21:21 ` Greg Freemyer
2010-05-28 22:06 ` H. Peter Anvin
2010-06-01 19:12 ` Eric Sandeen
2010-06-01 19:32 ` Sunil Mushran
2010-06-01 19:49 ` tytso
2010-06-01 20:14 ` Greg Freemyer
2010-06-01 21:00 ` Eric Sandeen [this message]
2010-06-01 21:28 ` Sunil Mushran
2010-06-01 22:26 ` tytso
2010-06-01 22:51 ` Sunil Mushran
2010-06-02 7:28 ` H. Peter Anvin
2010-06-02 18:02 ` Sunil Mushran
2010-06-08 22:12 ` H. Peter Anvin
2010-06-09 1:10 ` Joel Becker
2010-06-09 1:44 ` tytso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0574DF.3030303@redhat.com \
--to=sandeen@redhat.com \
--cc=Joel.Becker@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=sunil.mushran@oracle.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.