On Fri, Oct 31, 2025 at 1:42 PM Nicholas D Steeves <[email protected]> wrote:
>
> Control: tag -1 moreinfo
>
> Hi James,
>
> Reply follows in-line:
>
> James Young <[email protected]> writes:
>
> > Package: btrfs-progs
> > Version: 6.2-1+deb12u1
> > Severity: normal
> > X-Debbugs-Cc: [email protected]
> >
> > Dear Maintainer,
> >
> > My apologies if this has been handled by an update. I've skimmed Debian 
> > bugs, Github issues, and Github PRs without a match.
>
> Would you please try:
>
>   sudo apt install tee
>   echo "deb http://deb.debian.org/debian/ bookworm-backports main" \
>        | sudo tee /etc/apt/sources.list.d/bookworm-backports.list
>   sudo apt update
>   sudo apt install -t bookworm-backports btrfs-progs
>
> and share if the problem still occurs?

I did this, and, good news and bad news:
* bad: it's still an issue.
* good: I have suggestions.

Here's an excerpt of what I got with the updated version and a smaller
file system:
[1/8] checking log skipped (none written)
[1/7] checking root items                      (0:00:03 elapsed,
2944308 items checked)
[2/7] checking extents                         (0:00:05 elapsed, 30828
items checked)
[3/7] checking free space tree                 (0:00:00 elapsed, 81
items checked)
[4/7] checking fs roots                        (0:00:33 elapsed, 14014
items checked)
[5/7] checking csums (without verifying data)  (0:00:01 elapsed, 21003
items checked)
[6/7] checking root refs                       (0:00:00 elapsed, 3
items checked)
[8/8] checking quota groups skipped (not enabled on this FS)

If you look at it in a monospace font, the second column here all
start at character 48; it's not right-aligned, as I'd thought. The
character column furthest right is at character 88; using an earlier
count from a larger file system, it would've hit column 90, at least.

So, suggestions:
* as a workaround, always use a wide terminal
* emit the description and the status on separate lines, like:
[1/7] checking root items
  (0:00:03 elapsed, 2944308 items checked)


>
> > I was running `btrfs check —progress` on a file system, and its sensing of 
> > the terminal width started to misbehave.
> >
> > e.g. on part [1/7], a snippet:
> >           (1:12:23 elapsed, 536234248 items ch[1/7] checking root items
> >          (1:12:24 elapsed, 536387178 items ch[1/7] checking root items
> >         (1:12:25 elapsed, 536563300 items ch[1/7] checking root items
> >
> > I made the terminal a couple of characters wider in hopes it would at least 
> > line up better. (This didn’t help.)
> >
> > part [2/7], checking extents, was working better until I attempted to 
> > change the width to better recreate and capture the original width on part 
> > 1, then, well, a snippet:
> > tents                         (358:28:32 elapsed, 82 items checked[2/7] 
> > checking ext
> > ents                         (358:28:33 elapsed, 82 items checked[2/7] 
> > checking exte
> > nts                         (358:28:34 elapsed, 82 items checked[2/7] 
> > checking exten
> > ts                         (358:28:35 elapsed, 82 items checked[2/7] 
> > checking extent
> >
> > I expected the progress for each part to fit and stay on one line.
>
> What terminal are you using?  By chance is this a serial console or
> IPMI?  I periodically run btrfs check to make sure that it works
> properly and have never seen this.

This is iterm, ssh, and tmux; $TERM is tmux-256color.

Thanks -
-James

Reply via email to