* btrfs fi usage bug during shrink
@ 2016-08-01 4:00 Sean Greenslade
0 siblings, 0 replies; only message in thread
From: Sean Greenslade @ 2016-08-01 4:00 UTC (permalink / raw)
To: linux-btrfs
Hi, all. I was resizing (shrinking) a btrfs partition, and figured I'd
check in on how it was going with "btrfs fi usage." It was quite
startling:
$ sudo btrfs fi usage /mnt/
Overall:
Device size: 370.00GiB
Device allocated: 372.03GiB
Device unallocated: 16.00EiB
Device missing: 0.00B
Used: 360.56GiB
Free (estimated): 0.00B (min: 8.00EiB)
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 224.00MiB (used: 0.00B)
Data,single: Size:370.02GiB, Used:359.31GiB
/dev/mapper/c1 370.02GiB
Metadata,DUP: Size:1.00GiB, Used:639.22MiB
/dev/mapper/c1 2.00GiB
System,DUP: Size:8.00MiB, Used:64.00KiB
/dev/mapper/c1 16.00MiB
Unallocated:
/dev/mapper/c1 16.00EiB
It's reasonably obvious what's going on, here. The overall size has been
set to the final size, and now the worker is going through balancing all
the chunks that are now out of bounds.
I feel like "fi usage" should probably have some logic to detect this
situation and report something more sensible. Thankfully, it's only
transient, and returns to normal once the resize completes.
Thanks,
--Sean
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-08-01 4:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-08-01 4:00 btrfs fi usage bug during shrink Sean Greenslade
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).