From: Linda Knippers <linda.knippers@hp.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Chris Mason <chris.mason@oracle.com>, jim owens <jowens@hp.com>,
Diego Calleja <diegocg@gmail.com>,
Lee Trager <lt73@cs.drexel.edu>,
Christian Hesse <mail@earthworm.de>,
miguel.filipe@gmail.com, linux-btrfs@vger.kernel.org
Subject: Re: Selective Compression/Encryption
Date: Wed, 10 Dec 2008 13:02:56 -0500 [thread overview]
Message-ID: <49400450.2070703@hp.com> (raw)
In-Reply-To: <20081210175538.GA23225@infradead.org>
Christoph Hellwig wrote:
> 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*
The 'star' command has an -xattr option.
-- ljk
next prev parent reply other threads:[~2008-12-10 18:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 14:59 Selective Compression/Encryption Lee Trager
2008-12-09 15:45 ` Miguel Figueiredo Mascarenhas Sousa Filipe
[not found] ` <200812091722.21567.mail@earthworm.de>
2008-12-09 18:09 ` Lee Trager
2008-12-09 22:14 ` Miguel Figueiredo Mascarenhas Sousa Filipe
[not found] ` <1228863790.8130.14.camel@mattos-laptop>
2008-12-10 12:11 ` Miguel Figueiredo Mascarenhas Sousa Filipe
2008-12-09 23:05 ` Diego Calleja
2008-12-09 23:50 ` jim owens
2008-12-10 0:03 ` calin
2008-12-10 13:44 ` Chris Mason
2008-12-10 17:55 ` Christoph Hellwig
2008-12-10 18:02 ` Linda Knippers [this message]
2008-12-10 18:11 ` Joshua J. Berry
2008-12-10 9:06 ` Mattos, Oliver
2008-12-10 9:32 ` Jeremy Sanders
2008-12-10 12:19 ` Miguel Figueiredo Mascarenhas Sousa Filipe
2008-12-09 16:35 ` Chris Mason
2008-12-09 18:14 ` Lee Trager
2008-12-09 19:26 ` Joshua J. Berry
2008-12-09 20:22 ` jim owens
2008-12-10 13:45 ` Chris Mason
2008-12-10 14:33 ` btrfs with selinux jim owens
2008-12-11 22:03 ` Selective Compression/Encryption Lee Trager
2008-12-12 14:19 ` Chris Mason
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=49400450.2070703@hp.com \
--to=linda.knippers@hp.com \
--cc=chris.mason@oracle.com \
--cc=diegocg@gmail.com \
--cc=hch@infradead.org \
--cc=jowens@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lt73@cs.drexel.edu \
--cc=mail@earthworm.de \
--cc=miguel.filipe@gmail.com \
/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.