From: "David C. Partridge" <david.partridge@perdrix.co.uk>
To: "'Qu Wenruo'" <quwenruo.btrfs@gmx.com>,
<linux-btrfs@vger.kernel.org>,
"'Nikolay Borisov'" <nborisov@suse.com>
Subject: RE: Odd output from scrub status
Date: Mon, 18 Jul 2022 10:18:13 +0100 [thread overview]
Message-ID: <004901d89a87$500ea870$f02bf950$@perdrix.co.uk> (raw)
In-Reply-To: <38d342a0-9057-7fd7-6ed9-d9b07bc4c27c@gmx.com>
> Mind to share the following commands output?
Sure, no problem
root@charon:/home/amonra# btrfs fi df /shared
Data, single: total=8.37TiB, used=5.76TiB
System, DUP: total=32.00MiB, used=1.09MiB
Metadata, DUP: total=11.00GiB, used=5.56GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
root@charon:/home/amonra# btrfs fi usage /shared
Overall:
Device size: 25.46TiB
Device allocated: 8.39TiB
Device unallocated: 17.07TiB
Device missing: 0.00B
Used: 5.77TiB
Free (estimated): 19.68TiB (min: 11.14TiB)
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Data,single: Size:8.37TiB, Used:5.76TiB (68.89%)
/dev/sdb1 8.37TiB
Metadata,DUP: Size:11.00GiB, Used:5.56GiB (50.53%)
/dev/sdb1 22.00GiB
System,DUP: Size:32.00MiB, Used:1.09MiB (3.42%)
/dev/sdb1 64.00MiB
Unallocated:
/dev/sdb1 17.07TiB
root@charon:/home/amonra# uname -a
Linux charon 5.4.0-122-generic #138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
root@charon:/home/amonra#
David
next prev parent reply other threads:[~2022-07-18 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 11:28 Odd output from scrub status David C. Partridge
2022-07-18 8:01 ` Nikolay Borisov
2022-07-18 9:13 ` David C. Partridge
2022-07-18 8:05 ` Qu Wenruo
2022-07-18 9:18 ` David C. Partridge [this message]
2022-07-18 19:50 ` Chris Murphy
2022-07-19 0:01 ` David C. Partridge
2022-07-19 3:35 ` Chris Murphy
2022-07-19 16:32 ` David C. Partridge
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='004901d89a87$500ea870$f02bf950$@perdrix.co.uk' \
--to=david.partridge@perdrix.co.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=quwenruo.btrfs@gmx.com \
/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.