From: "Lluís Batlle i Rossell" <viric@viric.name>
To: Kyle Gates <kylegates@hotmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: State of nocow file attribute
Date: Wed, 15 Aug 2012 19:19:30 +0200 [thread overview]
Message-ID: <20120815171930.GI25996@vicerveza.homeunix.net> (raw)
In-Reply-To: <COL113-W11E89280DE29846698B431B0B60@phx.gbl>
On Wed, Aug 15, 2012 at 08:05:11AM -0500, Kyle Gates wrote:
> > Is there really a fix upstream for that? Do nocow attribute on files work for
> > anyone already?
>
> IIRC the nocow attribute seems to work if the volume is mounted with "nodatasum"
Shouldn't nocow mean also nodatasum *only for that file*? I find it a bit
useless, to require whole fs nodatasum for per-file nocow to work.
Thank you,
Lluís.
next prev parent reply other threads:[~2012-08-15 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 10:12 State of nocow file attribute Lluís Batlle i Rossell
[not found] ` <COL113-W11E89280DE29846698B431B0B60@phx.gbl>
2012-08-15 17:19 ` Lluís Batlle i Rossell [this message]
2012-08-17 1:45 ` Liu Bo
2012-08-17 14:59 ` David Sterba
2012-08-17 15:30 ` Liu Bo
2012-08-21 14:33 ` State of nocow file attribute David Sterba
2012-08-21 15:04 ` Liu Bo
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=20120815171930.GI25996@vicerveza.homeunix.net \
--to=viric@viric.name \
--cc=kylegates@hotmail.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).