From: M G Berberich <btrfs@oss.m-berberich.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Bug in 'btrfs filesystem du' ?
Date: Tue, 28 Jun 2016 14:56:39 +0200 [thread overview]
Message-ID: <20160628125639.GA6997@invalid> (raw)
In-Reply-To: <CAPmG0jbcojqdERe39Fnu20mg2e2VyxJOUi53Zy6kV_=B=q-zEA@mail.gmail.com>
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. The later kernel with two patches to make the kernel work:
https://lkml.org/lkml/2016/6/1/310 https://lkml.org/lkml/2016/6/1/311 .
You can see the script¹ I used (do-btrfs-du-test) and the logs at
http://m-berberich.de/btrfs/
In all four cases, ‘btrfs fi du -s .’ reports
Total Exclusive Set shared Filename
59.38MiB 0.00B 29.69MiB .
befor balance and
Total Exclusive Set shared Filename
59.38MiB 59.38MiB 0.00B .
after balance.
Disclaimer: The script works for me, no guaranty at all.
MfG
bmg
__________
¹ Disclaimer: The script works for me, no guaranty at all.
--
„Des is völlig wurscht, was heut beschlos- | M G Berberich
sen wird: I bin sowieso dagegn!“ | mail@m-berberich.de
(SPD-Stadtrat Kurt Schindler; Regensburg) |
next prev parent reply other threads:[~2016-06-28 12:56 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 [this message]
2016-06-28 16:55 ` Henk Slager
2016-06-28 17:20 ` Andrei Borzenkov
2016-06-29 4:07 ` Andrei Borzenkov
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=20160628125639.GA6997@invalid \
--to=btrfs@oss.m-berberich.de \
--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.