From: Chris Mason <chris.mason@oracle.com>
To: Yan Zheng <zheng.yan@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] New nodatacow checker
Date: Tue, 29 Jul 2008 23:18:22 +0000 [thread overview]
Message-ID: <1217373502.7572.142.camel@think.oraclecorp.com> (raw)
In-Reply-To: <3d0408630807291040t64a8518ne840f6c618ee7332@mail.gmail.com>
On Wed, 2008-07-30 at 01:40 +0800, Yan Zheng wrote:
> Hello,
>
> This is updated version of nodatacow patch. To check whether a given
> file extent is referenced by multiple snapshots, the checker walks
> down the fs tree through dead root and checks all tree blocks in the
> path. We can easily detect whether a given tree block is directly
> referenced by other snapshot. We can also detect any indirect
> reference from other snapshot by checking reference's generation. The
> checker can always detect multiple references, but can't reliably
> detect cases of single reference. So btrfs may do file data cow even
> there is only one reference.
>
Wonderful, thanks! I'll put this in tonight or tomorrow morning.
-chris
prev parent reply other threads:[~2008-07-29 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 17:40 [PATCH] New nodatacow checker Yan Zheng
2008-07-29 23:18 ` Chris Mason [this message]
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=1217373502.7572.142.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zheng.yan@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox