From: Chris Mason <chris.mason@oracle.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "Pádraig Brady" <p@draigbrady.com>, 8001 <8001@debbugs.gnu.org>,
"BTRFS MAILING LIST" <linux-btrfs@vger.kernel.org>
Subject: Re: bug#8001: cp (8.10) sparse handling fails on compressed btrfs (cp/fiemap-2)
Date: Tue, 22 Feb 2011 22:31:19 -0500 [thread overview]
Message-ID: <1298431849-sup-5365@think> (raw)
In-Reply-To: <AANLkTi=4x+RzqZRKVCreWy67eOUSocjA4c_N+9aEHeG9@mail.gmail.com>
Excerpts from Mike Frysinger's message of 2011-02-19 19:53:18 -0500:
> 2011/2/19 P=C3=A1draig Brady:
> > On 19/02/11 18:28, Mike Frysinger wrote:
> >> based on other threads (which i havent been following too closely)=
, did we
> >> settle on this being a btrfs bug ?
> >
> > Nope, cp 8.10 is not absolved yet.
> > It may be btrfs not honoring FIEMAP_FLAG_SYNC,
> > and/or it may be cp needing to handle FIEMAP_EXTENT_ENCODED
> > specially.
> >
> > It would help if you ran `sync` before the copy,
> > to exclude that as a possible issue.
>=20
> makes no difference after applying this patch:
I've got a fix for this on the btrfs side in testing. It is definitely
a btrfs bug.
-chris
--
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:[~2011-02-23 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201102072253.34476.vapier@gentoo.org>
2011-02-09 10:57 ` bug#8001: cp (8.10) sparse handling fails on compressed btrfs (cp/fiemap-2) Pádraig Brady
2011-02-19 18:28 ` Mike Frysinger
2011-02-19 23:22 ` Pádraig Brady
2011-02-20 0:39 ` Pádraig Brady
2011-02-20 0:53 ` Mike Frysinger
2011-02-23 3:31 ` Chris Mason [this message]
2011-02-23 9:49 ` Pádraig Brady
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=1298431849-sup-5365@think \
--to=chris.mason@oracle.com \
--cc=8001@debbugs.gnu.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=p@draigbrady.com \
--cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.