From: "Pádraig Brady" <P@draigBrady.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: BTRFS MAILING LIST <linux-btrfs@vger.kernel.org>, 8001@debbugs.gnu.org
Subject: Re: bug#8001: cp (8.10) sparse handling fails on compressed btrfs (cp/fiemap-2)
Date: Sun, 20 Feb 2011 00:39:47 +0000 [thread overview]
Message-ID: <4D6062D3.3090905@draigBrady.com> (raw)
In-Reply-To: <4D6050A7.5090407@draigBrady.com>
On 19/02/11 23:22, P=E1draig Brady wrote:
> On 19/02/11 18:28, Mike Frysinger wrote:
>> based on other threads (which i havent been following too closely), =
did we=20
>> settle on this being a btrfs bug ?
>> -mike
>=20
> 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.
>=20
> It would help if you ran `sync` before the copy,
> to exclude that as a possible issue.
>=20
> Also `filefrag -v` output for the file on
> the compressed BTRFS file system would be helpful.
Hmm I just tried the latest Fedora 15 live image
and was tripped up a bit by https://bugzilla.redhat.com/show_bug.c
Anyway it uses 2.6.38 rc4 and "compress" doesn't
seem to be implemented for BTRFS there?
Writing a file of zeros showed a normal disk usage,
and filefrag -v didn't report any flags for the extents.
In any case, cp/fiemap-2 passed on each of
about 100 runs, even without introducing
and syncs.
cheers,
P=E1draig.
--
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-20 0:39 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 [this message]
2011-02-20 0:53 ` Mike Frysinger
2011-02-23 3:31 ` Chris Mason
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=4D6062D3.3090905@draigBrady.com \
--to=p@draigbrady.com \
--cc=8001@debbugs.gnu.org \
--cc=linux-btrfs@vger.kernel.org \
--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.