From: Coly Li <i@coly.li>
To: liubo <liubo2009@cn.fujitsu.com>
Cc: ext4 <linux-ext4@vger.kernel.org>,
Linux Btrfs <linux-btrfs@vger.kernel.org>, tytso <tytso@mit.edu>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH 1/2] E2fsprogs: use the generic inode flags
Date: Mon, 18 Apr 2011 19:15:41 +0800 [thread overview]
Message-ID: <4DAC1D5D.3020506@coly.li> (raw)
In-Reply-To: <4DABFDF0.9060608@cn.fujitsu.com>
On 2011年04月18日 17:01, liubo Wrote:
> On 04/18/2011 04:41 PM, Coly Li wrote:
>> On 2011年04月18日 15:37, liubo Wrote:
>>> Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
>>> ---
>>> debugfs/htree.c | 2 +-
>>> e2fsck/pass1.c | 22 +++++++++++-----------
>>> e2fsck/pass2.c | 2 +-
>>> e2fsck/pass4.c | 2 +-
>>> e2fsck/rehash.c | 4 ++--
>>> ext2ed/inode_com.c | 14 +++++++-------
>>> lib/e2p/fgetflags.c | 6 +++---
>>> lib/e2p/fsetflags.c | 6 +++---
>>> lib/e2p/getflags.c | 6 +++---
>>> lib/e2p/pf.c | 34 +++++++++++++++++-----------------
>>> lib/e2p/setflags.c | 6 +++---
>>> lib/ext2fs/ext2_fs.h | 44 ++++++++++++++++++++++----------------------
>>> lib/ext2fs/link.c | 4 ++--
>>> lib/ext2fs/mkjournal.c | 2 +-
>>> misc/chattr.c | 26 +++++++++++++-------------
>>> misc/tune2fs.c | 2 +-
>>> 16 files changed, 91 insertions(+), 91 deletions(-)
>>> [snip]
>>
>> Hi Bo,
>>
>> Could you please to introduce the motivation of this patch set a little bit more? Thanks.
>>
>
> Hi Li,
>
> Since we want to control COW and compression attribute on a per file or per directory basis,
> and find that the generic command "chattr" is the "Mr Right".
>
> Currently only btrfs supports both, of course.
>
> With these patches, we can do the followings:
>
> c: compress
> C: nocow
>
> set compress & nocow:
>
> # ./misc/chattr -V +c +C /mnt/btrfs/dir/
> chattr 1.41.14 (22-Dec-2010)
> Flags of /mnt/btrfs/dir/ set as --------c------C
>
> # ./misc/lsattr -d /mnt/btrfs/dir/
> --------c------C /mnt/btrfs/dir/
>
Thank you for the explaining. Now I understand this patch set is to make chattr of e2fsprogs to support a
(currently-only) btrfs feature.
It seems chattr and lsattr is not an ext[234] only utilities any more...
--
Coly Li
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-18 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DA2A0CC.9000301@cn.fujitsu.com>
2011-04-18 7:37 ` [PATCH 1/2] E2fsprogs: use the generic inode flags liubo
2011-04-18 8:41 ` Coly Li
2011-04-18 9:01 ` liubo
2011-04-18 11:15 ` Coly Li [this message]
2011-04-18 10:51 ` Christoph Hellwig
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=4DAC1D5D.3020506@coly.li \
--to=i@coly.li \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).