All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chester <somethingsome2000@gmail.com>
To: Ralf-Peter Rohbeck <rohbeck@yahoo.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Set nodatacow per file?
Date: Mon, 13 Feb 2012 01:34:52 -0600	[thread overview]
Message-ID: <CAAE6i0iHNnr7=BjFOWd8hR99jKKVAfGcFo5GKHLnT6nytWn7jA@mail.gmail.com> (raw)
In-Reply-To: <4F38B8F0.5020506@yahoo.com>

On Mon, Feb 13, 2012 at 1:17 AM, Ralf-Peter Rohbeck <rohbeck@yahoo.com>=
 wrote:
>
> Hello,
> is it possible to set nodatacow on a per-file basis? I couldn't find =
anything.
> If not, wouldn't that be a great feature to get around the performanc=
e issues with VM and database storage? Of course cloning should still c=
ause COW.

IIRC this is already a feature in btrfs. I didn't catch the whole
talk, but Chris mentioned something like this at Scale 10x. I also
remember seeing a patch for it a while back (I think it was from liu
bo) that does this.

>
> Thanks,
> Ralf-Peter
> --
> 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 =A0http://vger.kernel.org/majordomo-info.html
--
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

  reply	other threads:[~2012-02-13  7:34 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 [this message]
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
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='CAAE6i0iHNnr7=BjFOWd8hR99jKKVAfGcFo5GKHLnT6nytWn7jA@mail.gmail.com' \
    --to=somethingsome2000@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rohbeck@yahoo.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.