From: Liu Bo <bo.li.liu@oracle.com>
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: Btrfs mailing list <linux-btrfs@vger.kernel.org>,
David Sterba <dave@jikos.cz>
Subject: Re: State of nocow file attribute
Date: Fri, 17 Aug 2012 09:45:20 +0800 [thread overview]
Message-ID: <502DA230.6010202@oracle.com> (raw)
In-Reply-To: <20120815101229.GH25996@vicerveza.homeunix.net>
On 08/15/2012 06:12 PM, Lluís Batlle i Rossell wrote:
> Hello,
>
> some time ago we discussed on #btrfs that the nocow attribute for files wasn't
> working (around 3.3 or 3.4 kernels). That was evident by files fragmenting even
> with the attribute set.
>
> Chris mentioned to find a fix quickly for that, and posted some lines of change
> into irc. But recently someone mentioned that 3.6-rc looks like still not
> respecting nocow for files.
>
> Is there really a fix upstream for that? Do nocow attribute on files work for
> anyone already?
>
Hi Lluís,
Dave had post a patch to fix it but only enabling NOCOW with zero sized file.
FYI, the patch is http://article.gmane.org/gmane.comp.file-systems.btrfs/17351
With the patch, you don't need to mount with nodatacow any more :)
And why it is only for only zero sized file:
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/18046
thanks,
liubo
> Regards,
> Lluís.
> --
> 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-08-17 1:47 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
2012-08-17 1:45 ` Liu Bo [this message]
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=502DA230.6010202@oracle.com \
--to=bo.li.liu@oracle.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=viric@viric.name \
/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).