From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Henk Slager <eye1tm@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Bug in 'btrfs filesystem du' ?
Date: Wed, 29 Jun 2016 07:07:16 +0300 [thread overview]
Message-ID: <57734974.4050405@gmail.com> (raw)
In-Reply-To: <5772B1FA.5010004@gmail.com>
28.06.2016 20:20, Andrei Borzenkov пишет:
> 28.06.2016 19:55, Henk Slager пишет:
>> On Tue, Jun 28, 2016 at 2:56 PM, M G Berberich <btrfs@oss.m-berberich.de> wrote:
>>> Hello,
>>>
>>> Am Montag, den 27. Juni schrieb Henk Slager:
>>>> On Mon, Jun 27, 2016 at 3:33 PM, M G Berberich <btrfs@oss.m-berberich.de> wrote:
>>>>> Am Montag, den 27. Juni schrieb M G Berberich:
>>>>>> after a balance ‘btrfs filesystem du’ probably shows false data about
>>>>>> shared data.
>>>>>
>>>>> Oh, I forgot: I have btrfs-progs v4.5.2 and kernel 4.6.2.
>>>>
>>>> With btrfs-progs v4.6.1 and kernel 4.7-rc5, the numbers are correct
>>>> about shared data.
>>>
>>> I tested with kernels 4.6.3 and 4.7-rc5 and with btrfs-progs 4.5.2 and
>>> 4.61.
>> Also with kernel 4.6.2-1-default and btrfs-progs v4.5.3+20160516
>> (current stock opensuse tumbleweed) I cannot reproduce the problem.
>>
>
> I confirm the same behavior on openSUSE Tumbleweed with kernel 4.6.2-1.2
> and btrfsprogs 4.5.3-1.2 using provided script.
>
I realized that it sounded ambiguous. I do see the reported bug on
openSUSE Tumbleweed using the same versions as you. After rebalance
shared data disappears completely in du output.
prev parent reply other threads:[~2016-06-29 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 13:28 Bug in 'btrfs filesystem du' ? M G Berberich
2016-06-27 13:33 ` M G Berberich
2016-06-27 18:48 ` Henk Slager
2016-06-28 12:56 ` M G Berberich
2016-06-28 16:55 ` Henk Slager
2016-06-28 17:20 ` Andrei Borzenkov
2016-06-29 4:07 ` Andrei Borzenkov [this message]
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=57734974.4050405@gmail.com \
--to=arvidjaar@gmail.com \
--cc=eye1tm@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).