From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: Selective Compression/Encryption Date: Wed, 10 Dec 2008 12:55:38 -0500 Message-ID: <20081210175538.GA23225@infradead.org> References: <20081209145952.GA30494@tux64-03> <200812091722.21567.mail@earthworm.de> <20081209180951.GA6551@tux64-03> <20081210000512.7be20413@diego-desktop> <493F043B.50804@hp.com> <1228916687.11900.10.camel@think.oraclecorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: jim owens , Diego Calleja , Lee Trager , Christian Hesse , miguel.filipe@gmail.com, linux-btrfs@vger.kernel.org To: Chris Mason Return-path: In-Reply-To: <1228916687.11900.10.camel@think.oraclecorp.com> List-ID: On Wed, Dec 10, 2008 at 08:44:47AM -0500, Chris Mason wrote: > I had planned to make the bits inheritable from the directory inode > flags. There are two different discussions around xattrs for this. One > is using xattrs to store the flag, which I'd would rather avoid because > it is checked in some performance critical places. > > The second is using xattr programs to set the flag, which I don't really > have an opinion on. The idea of having the flags backed up by backup > programs or rsync is really nice, but do any of the backup programs > actually copy out all the xattrs? xfsdump does :) But I think especially the compressed bit is much better off in the bit for the set/get flags ioctls used by chattr / lsattr. These are implemented by all Linux filesystems, and even have a compressed bit allocated already. (and xfsdump of course backs them up, too ;-)) *run*