From: Ryan Bourne <hub@spotprint.com.au>
To: linux-btrfs@vger.kernel.org
Subject: Re: running duperemove but no free space gain
Date: Tue, 07 Jul 2015 16:27:36 +1000 [thread overview]
Message-ID: <559B7158.6050404@spotprint.com.au> (raw)
In-Reply-To: <20150706230725.GG7507@wotan.suse.de>
On 7/07/15 9:07 AM, Mark Fasheh wrote:
>
> Yes I forgot about that but in your case almost everything will be reported
> shared. Btw, I have to leave my office now but will get to the rest of your e-mail
> later.
>
> --
> Mark Fasheh
> --
To clarify, if I did the following:
# btrfs subvolume create a
# dd bs=1M count=10 if=/dev/urandom of=a/1
# dd if=a/1 of=a/2
# btrfs subvolume snapshot a b
then I have four files containing the same data. a/1, b/1 share extents
and a/2, b/2 share extents.
If I then deduplicate a/1 and a/2 will all four files be sharing
extents, or only three? (Assuming I have the patches for 4.2)
next prev parent reply other threads:[~2015-07-07 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 21:54 running duperemove but no free space gain Mordechay Kaganer
2015-07-06 22:34 ` Mark Fasheh
2015-07-06 23:03 ` Mordechay Kaganer
2015-07-06 23:07 ` Mark Fasheh
2015-07-07 6:27 ` Ryan Bourne [this message]
2015-07-07 13:14 ` Mordechay Kaganer
2015-07-08 5:57 ` Mordechay Kaganer
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=559B7158.6050404@spotprint.com.au \
--to=hub@spotprint.com.au \
--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 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.