From: Kent Overstreet <kent.overstreet@linux.dev>
To: Jan Engelhardt <ej@inai.de>
Cc: linux-bcachefs@vger.kernel.org
Subject: Re: `bcachefs fs usage` is missing some spaces
Date: Sat, 17 Jan 2026 15:17:58 -0500 [thread overview]
Message-ID: <aWvuCklhJsxxWymV@moria.home.lan> (raw)
In-Reply-To: <8sq99o96-0755-r095-o410-o6n1o4oq228s@vanv.qr>
On Fri, Jan 09, 2026 at 04:10:22PM +0100, Jan Engelhardt wrote:
>
> Kernel component: 1.33.4
> Userspace component: 1.34.0 (also with 1.33.4)
>
> ```
> # bcachefs fs usage /var/lib/lancache
> Filesystem: c5ac2bf7-79a9-484d-8886-5188cb3168e7
> Size: 5549130619392
> Used: 2488634602496
> Online reserved: 114860032
>
> Data by durability desired and amount degraded:
> undegraded
> 1x: 2467920244736
> 2x: 20597702656
>
> Device label Device State Size Used Use%
> hdd.hdd0 (device 2): sde rw 10002030919687816089600 00%
> hdd.hdd1 (device 3): sdf rw 10002030919687816089600 00%
> ssd.ssd0 (device 0): sdd rw 96019572326463255844454465%
> ssd.ssd1 (device 1): sda rw 96019572326463252830208065%
> ssd.ssd2 (device 4): sdh rw 96019572326463251319603265%
> ssd.ssd3 (device 6): sdb rw 96019677184062093350912064%
> ```
>
> There are some spaces missing in the output. It is not readable this way.
>
> # blockdev --getsize64 /dev/sde: 1000204886016
> # blockdev --getsize64 /dev/sdb: 960197124096
>
> So that's what the number should be close to.
There's an outstanding pull request I've been _really_ lazy about
reviewing - adds flexible tabstops:
https://github.com/koverstreet/bcachefs-tools/pull/488
Maybe I'll do that tomorrow.
prev parent reply other threads:[~2026-01-17 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 15:10 `bcachefs fs usage` is missing some spaces Jan Engelhardt
2026-01-17 20:17 ` Kent Overstreet [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=aWvuCklhJsxxWymV@moria.home.lan \
--to=kent.overstreet@linux.dev \
--cc=ej@inai.de \
--cc=linux-bcachefs@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