From: dima <dolenin@parallels.com>
To: <linux-btrfs@vger.kernel.org>
Subject: Re: Set nodatacow per file?
Date: Tue, 14 Feb 2012 00:10:23 +0900 [thread overview]
Message-ID: <4F3927DF.3020401@parallels.com> (raw)
In-Reply-To: <20120213141040.GG15350@twin.jikos.cz>
On 02/13/2012 11:10 PM, David Sterba wrote:
> Hi,
>
> On Mon, Feb 13, 2012 at 04:40:03PM +0900, dima wrote:
>> Actually it is possible. Check out David's response to my question from
>> some time ago:
>> http://permalink.gmane.org/gmane.comp.file-systems.btrfs/14227
>
> this was a quick aid, please see attached file for an updated tool to set
> the file flags, now added 'z' for NOCOMPRESS flag, and supports chattr
> syntax plus all of the standard file flags.
>
> Setting and unsetting nocow is done like 'fileflags +C file' or -C for
> unseting. Without any + or - options it prints current state.
>
>
> david
Thanks David. Perfect! This would be a great help.
~dima
next prev parent reply other threads:[~2012-02-13 15:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 7:17 Set nodatacow per file? Ralf-Peter Rohbeck
2012-02-13 7:34 ` Chester
2012-02-13 8:10 ` Liu Bo
2012-02-13 7:40 ` dima
2012-02-13 8:09 ` Roman Mamedov
2012-02-13 8:40 ` dima
2012-02-13 13:42 ` dima
2012-02-13 13:51 ` Roman Mamedov
2012-02-13 14:31 ` Dmitry Olenin
2012-02-13 14:10 ` David Sterba
2012-02-13 14:21 ` Timo Witte
2012-02-13 15:10 ` dima [this message]
2012-02-16 13:55 ` NOCOW + compress-force = bug Roman Mamedov
2012-02-16 14:30 ` David Sterba
2012-02-16 17:58 ` Chris Mason
2012-03-13 18:11 ` Jeff Mahoney
2012-03-13 18:36 ` Jeff Mahoney
2012-02-29 15:09 ` Set nodatacow per file? Kyle Gates
2012-02-29 15:34 ` cwillu
2012-02-24 5:22 ` dima
2012-02-27 13:54 ` dima
2012-02-27 22:10 ` Chester
2012-02-28 0:51 ` dima
2012-03-02 3:28 ` dima
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=4F3927DF.3020401@parallels.com \
--to=dolenin@parallels.com \
--cc=linux-btrfs@vger.kernel.org \
/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.