All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: dima <dolenin@parallels.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Set nodatacow per file?
Date: Mon, 13 Feb 2012 19:51:16 +0600	[thread overview]
Message-ID: <20120213195116.26e64e16@natsu> (raw)
In-Reply-To: <4F39133F.50908@parallels.com>

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

On Mon, 13 Feb 2012 22:42:23 +0900
dima <dolenin@parallels.com> wrote:

> > gcc -o /usr/local/bin/nocow nocow.c
> > ln -sf /usr/local/bin/nocow /usr/local/bin/cow

> I don't seem to be able to 'unset' the NOCOW flag.  Looking at the code 
> I would guess that it is supposed to alternate between 'cow' and 'nocow' 
> states, but the condition
>      printf("Remove NOCOW flag for %s\n", argv[1]);
> never shows for me. What should I do to make it working?
> Maybe it would be nice to have a switch to just check if nocow is set on 
> file without actually changing the flag.

If you place it in /usr/local/bin and also make a symlink "nocow -> cow" as
described in the quoted part above, you can then just run: 

# cow ./filename

and the program will instead unset the NOCOW flag.

Of course it remains to be a very basic program, I'm not sure if it's worth
developing it further, or to add this to 'btrfs', as Liu Bo in the adjacent
thread said that there are patches to chattr/lsattr for using the COW
attribute.

-- 
With respect,
Roman

~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-02-13 13:51 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 [this message]
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
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=20120213195116.26e64e16@natsu \
    --to=rm@romanrm.ru \
    --cc=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.