On Sun, Dec 4, 2016 at 7:30 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
> Hi,
>
> [chris@f25s ~]$ uname -r
> 4.8.11-300.fc25.x86_64
> [chris@f25s ~]$ rpm -q btrfs-progs
> btrfs-progs-4.8.5-1.fc26.x86_64
>
>
> I'm not finding any pattern to this so far, but it's definitely not
> always reliable. Here is today's example.
>
> [chris@f25s ~]$ sudo btrfs fi du -s /mnt/second/jackson.2015/
> Total Exclusive Set shared Filename
> 111.67GiB 111.67GiB 0.00B /mnt/second/jackson.2015/
>
> Super. This is correct. The jackson.2015 subvolume contains only
> exclusively used data, there are no snapshots, and there are no
> reflinks involved for any files.
>
>
> [chris@f25s ~]$ sudo btrfs send /mnt/second/jackson.2015/ | sudo
> btrfs receive /mnt/int/
>
> Send the subvolume to a different btrfs volume. This is not an
> incremental send. After completion however:
>
>
> [chris@f25s ~]$ sudo btrfs fi du -s /mnt/int/jackson.2015/
> Total Exclusive Set shared Filename
> 111.67GiB 37.20GiB 29.93GiB /mnt/int/jackson.2015/
>
> That makes zero sense. What's going on here?
I tried to reproduce, with progs from git v4.8.5 and kernel
4.8.10-1-default (tumbleweed):
# /net/src/btrfs-progs/btrfs send testfidu |
/net/src/btrfs-progs/btrfs receive /local/omedia/
# /net/src/btrfs-progs/btrfs fi du -s ./testfidu/
Total Exclusive Set shared Filename
42.56GiB 42.56GiB 0.00B ./testfidu/
# /net/src/btrfs-progs/btrfs fi du -s /local/omedia/testfidu/
Total Exclusive Set shared Filename
42.56GiB 42.56GiB 0.00B /local/omedia/testfidu/
There are no btrfs changes between kernels 4.8.10 and 4.8.11. There is
no compress mount option in my case, that is the only thing I
currently can think of that could make your Set shared number
non-zero.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
