From: Giuseppe Scrivano <gscrivano@gnu.org>
To: "Pádraig Brady" <P@draigBrady.com>
Cc: bug-coreutils@gnu.org, Jim Meyering <jim@meyering.net>,
linux-btrfs@vger.kernel.org
Subject: Re: BTRFS file clone support for cp
Date: Tue, 28 Jul 2009 22:06:35 +0200 [thread overview]
Message-ID: <8763dcvagk.fsf@master.homenet> (raw)
In-Reply-To: <4A6E3ADE.6050008@draigBrady.com> ("Pádraig Brady"'s message of "Tue, 28 Jul 2009 00:40:14 +0100")
Hi P=C3=A1draig,
P=C3=A1draig Brady <P@draigBrady.com> writes:
> How different exactly?
> OK I tried this myself on F11 with inconclusive results.
I can't replicate it now, all tests I am doing report that blocks used
before and after the clone are the same. Probably yesterday the
difference I noticed was in reality the original file flushed to the
disk.
> The above suggests that the clone does actually allocate space
> but btrfs isn't reporting it through statvfs correctly?
The same message appeared here too some days ago, though I cloned only
few Kb files, not much to fill the entire partition.
> If the clone does allocate space, then how can one
> clone without allocation which could be very useful
> for snapshotting for example?
I don't know if snapshotting is handled in the same way as a "clone",
but in this case it seems more obvious to me that no additional space
should be reported.
> Also I tried the above twice and both times got:
> http://www.kerneloops.org/submitresult.php?number=3D578993
I didn't get these errors. I am using the btrfs git version.
Regards,
Giuseppe
next prev parent reply other threads:[~2009-07-28 20:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87d47o3fip.fsf@master.homenet>
[not found] ` <4A6CEA48.5050208@draigBrady.com>
[not found] ` <8763defuvq.fsf@meyering.net>
[not found] ` <87ws5tvrq8.fsf@master.homenet>
2009-07-27 23:40 ` BTRFS file clone support for cp Pádraig Brady
2009-07-28 20:06 ` Giuseppe Scrivano [this message]
2009-07-29 13:01 ` Chris Mason
2009-07-29 14:14 ` Pádraig Brady
2009-07-29 16:10 ` Chris Mason
2009-07-29 16:18 ` Chris Mason
2009-07-29 18:14 ` Pádraig Brady
2009-07-30 0:57 ` Joel Becker
2009-07-30 7:39 ` Jim Meyering
2009-07-30 8:21 ` Joel Becker
2009-07-30 8:40 ` Pádraig Brady
2009-07-30 16:28 ` Ric Wheeler
2009-07-30 16:48 ` Jim Meyering
2009-07-30 9:26 ` Andi Kleen
2009-07-30 10:02 ` Pádraig Brady
2009-07-30 10:16 ` Jim Meyering
2009-07-30 10:21 ` Tomasz Chmielewski
2009-07-30 10:54 ` Andi Kleen
2009-07-30 18:05 ` Joel Becker
2009-07-30 23:28 ` Pádraig Brady
[not found] ` <87k51r9sxh.fsf@master.homenet>
[not found] ` <4A70C4E0.9030104@draigBrady.com>
2009-07-30 17:28 ` Giuseppe Scrivano
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=8763dcvagk.fsf@master.homenet \
--to=gscrivano@gnu.org \
--cc=P@draigBrady.com \
--cc=bug-coreutils@gnu.org \
--cc=jim@meyering.net \
--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