From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?P=E1draig_Brady?= <P@draigBrady.com>
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
Message-ID: <4D6062D3.3090905@draigBrady.com>
References: <201102072253.34476.vapier@gentoo.org>	<4D52730A.2080008@draigBrady.com>	<201102191328.42067.vapier@gentoo.org> <4D6050A7.5090407@draigBrady.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Cc: BTRFS MAILING LIST <linux-btrfs@vger.kernel.org>,
	8001@debbugs.gnu.org
To: Mike Frysinger <vapier@gentoo.org>
Return-path: <linux-btrfs-owner@vger.kernel.org>
In-Reply-To: <4D6050A7.5090407@draigBrady.com>
List-ID: <linux-btrfs.vger.kernel.org>

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