From: Goffredo Baroncelli <kreijack@libero.it>
To: kreijack@inwind.it
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Liu Bo <liubo2009@cn.fujitsu.com>, "Ted Ts'o" <tytso@mit.edu>
Subject: Re: Btrfs and data nocow per inode basis
Date: Tue, 12 Jun 2012 19:41:25 +0200 [thread overview]
Message-ID: <4FD77F45.3060000@libero.it> (raw)
In-Reply-To: <4FD442F1.7040008@inwind.it>
On 06/10/2012 08:47 AM, Goffredo Baroncelli wrote:
> Hi all,
>
> which is the supposed corrected way to set the file flag FS_NOCOW_FL ? I
> know that exists the associated ioctl FS_IOC_SETFLAGS; which I didn't
> found is an user-space tool to use to set the flags.
>
> I am missing something ?
After a bit of googling I found a Liu Bo patches which add the ability
to set the NOCOW flags to a btrfs file.[1]
However it seems that it was not present in the current (v1.42.3)
e2fsprogs suite.
There is any reason which stopped the adoption of this patch ?
Does make sense to add the chattr/lsattr capability to the btrfs tool (I
am thinking about new commands like "btrfs filesystem chattr"/"btrfs
filesystem lsattr") ?
G.Baroncelli
[1] http://patchwork.ozlabs.org/patch/91697/
>
> Thanks in advance
> G.Baroncelli
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" 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:[~2012-06-12 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 6:47 Btrfs and data nocow for per inode basis Goffredo Baroncelli
2012-06-12 17:41 ` Goffredo Baroncelli [this message]
2012-06-12 18:32 ` Btrfs and data nocow " Ted Ts'o
2012-06-12 19:15 ` Ted Ts'o
2012-06-12 20:44 ` Chris Mason
2012-06-12 21:02 ` Goffredo Baroncelli
2012-06-12 21:10 ` Ted Ts'o
2012-06-12 22:19 ` Ted Ts'o
2012-06-13 7:42 ` Liu Bo
2012-06-12 22:08 ` David Sterba
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=4FD77F45.3060000@libero.it \
--to=kreijack@libero.it \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@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).