From: dima <dolenin@parallels.com>
To: <linux-btrfs@vger.kernel.org>
Subject: Re: Set nodatacow per file?
Date: Mon, 13 Feb 2012 16:40:03 +0900 [thread overview]
Message-ID: <4F38BE53.4080204@parallels.com> (raw)
In-Reply-To: <4F38B8F0.5020506@yahoo.com>
Hello Ralf-Peter,
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
The nocow.c script he attached does just the thing you want. The script
is really working. I needed nocow for different purpose but it did not
occur to me to try it on VM image and see if the performance would
improve. Sounds like a great idea. If you get around to try it, pls.
post your impressions here.
best
~dima
On 02/13/2012 04:17 PM, Ralf-Peter Rohbeck 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 performance
> issues with VM and database storage? Of course cloning should still
> cause COW.
>
> 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 http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-02-13 7:40 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 [this message]
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=4F38BE53.4080204@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 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).