From: tytso@mit.edu Subject: Re: e4defrag and immutable files Date: Tue, 1 Jun 2010 15:49:24 -0400 Message-ID: <20100601194924.GF4426@thunk.org> References: <4C002427.3010706@zytor.com> <4C05604D.2070401@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "H. Peter Anvin" , linux-ext4@vger.kernel.org, Joel Becker , Mark Fasheh To: Sunil Mushran Return-path: Received: from thunk.org ([69.25.196.29]:43361 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751635Ab0FATt0 (ORCPT ); Tue, 1 Jun 2010 15:49:26 -0400 Content-Disposition: inline In-Reply-To: <4C05604D.2070401@oracle.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: 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