From: Liu Bo <liubo2009@cn.fujitsu.com>
To: Kyle Gates <kylegates@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: balance disables nodatacow
Date: Tue, 31 Jul 2012 10:00:23 +0800 [thread overview]
Message-ID: <50173C37.9090607@cn.fujitsu.com> (raw)
In-Reply-To: <CA+M2DjmS0xB8zinvELi5SBg1QRxabvHfpd1MqJxqCB65qq1ceA@mail.gmail.com>
On 07/31/2012 03:55 AM, Kyle Gates wrote:
> I have a 3 disk raid1 filesystem mounted with nodatacow. I have a
> folder in said filesystem with the 'C' NOCOW & 'Z' Not_Compressed
> flags set for good measure. I then copy in a large file and proceed to
> make random modifications. Filefrag shows no additional extents
> created, good so far. A big thank you to the those devs who got that
> working.
> However, after a balance run (which crashed btw), modifications to the
> file result in increasing extent counts, ie. no longer obeying
> nodatacow mount option nor the 'C' flag.
> I realize that a balance will cow the data but it should not disable
> the ability to make nodatacow inline changes to a file.
>
> I'm currently running 3.5.0 mainline Ubuntu kernel with the latest
> master of btrfs-progs from a ppa.
>
hmm, I want to know if your 3.5.0 mainline ubuntu kernel has the commit:
Btrfs: make btrfs's allocation smoothly with preallocation
This commit may help you out of trouble.
Please let us know the result.
thanks,
liubo
> Thank you.
> Kyle Gates
> --
> 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-07-31 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 19:55 balance disables nodatacow Kyle Gates
2012-07-31 2:00 ` Liu Bo [this message]
2012-07-31 4:35 ` Kyle Gates
2012-07-31 4:58 ` Liu Bo
2012-08-02 3:14 ` Kyle Gates
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=50173C37.9090607@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=kylegates@gmail.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).