From: Maxime Devos <maximedevos@telenet.be>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 47379@debbugs.gnu.org
Subject: bug#47379: "statfs" test in tests/syscall.scm fails with BTRFS file systems.
Date: Thu, 25 Mar 2021 11:16:25 +0100 [thread overview]
Message-ID: <2cca61a298fd7481859a7268fbe98fc046fff736.camel@telenet.be> (raw)
In-Reply-To: <YFxgGjhK36kJ8nn6@3900XT>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On Thu, 2021-03-25 at 12:04 +0200, Efraim Flashner wrote:
> [...]
> I'm also running on btrfs
> (ins)scheme@(guile-user)> (statfs "/")
> [...]
>
> (ins)efraim@3900XT ~$ btrfs filesystem df /
> Data, single: total=289.00GiB, used=287.83GiB
> System, single: total=32.00MiB, used=48.00KiB
> Metadata, single: total=13.00GiB, used=12.07GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
>
> When was the last time you ran btrfs balance?
... never? My output of "btrfs filesystem df" FWIW:
$ btrfs filesystem df /
Data, single: total=224.01GiB, used=223.14GiB
System, DUP: total=8.00MiB, used=48.00KiB
Metadata, DUP: total=14.00GiB, used=13.81GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
Are there any reasons for running "btrfs balance"?
If so, what command do you recommend (I assume something
only touching meta data?)
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-03-25 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 8:49 bug#47379: "statfs" test in tests/syscall.scm fails with BTRFS file systems Maxime Devos
2021-03-25 10:04 ` Efraim Flashner
2021-03-25 10:16 ` Maxime Devos [this message]
2021-03-25 10:25 ` Efraim Flashner
2021-03-26 12:22 ` raid5atemyhomework via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cca61a298fd7481859a7268fbe98fc046fff736.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=47379@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).