Bug 511799 - Error output isn't useful if shrink stops at the filesystem check phase
Summary: Error output isn't useful if shrink stops at the filesystem check phase
Status: REPORTED
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.08.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-07 23:30 UTC by Ellie
Modified: 2025-11-07 23:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
A screenshot of the full report seen in an external web browser, showing "Error". (135.45 KB, image/png)
2025-11-07 23:30 UTC, Ellie
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ellie 2025-11-07 23:30:38 UTC
Created attachment 186600 [details]
A screenshot of the full report seen in an external web browser, showing "Error".

SUMMARY

My apologies if I'm missing something here, but the error output doesn't seem to be useful if shrink stops at the filesystem check phase. The expected error output in my opinion would be whatever "btrfs check" actually said, but instead it says "Error" and nothing else. Or am I missing something?

STEPS TO REPRODUCE

1. Try to shrink a filesystem
2. It checks the filesystem first
3. "Error"...?

OBSERVED RESULT

"Error"

EXPECTED RESULT

The output of the filesystem check tool so I can see what even happened and what it found to be wrong.

SOFTWARE/OS VERSIONS

Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: postmarketOS Edge
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.3

ADDITIONAL INFORMATION
Comment 1 Andrius Štikonas 2025-11-07 23:35:31 UTC
Yeah, we need to print errors and print more output from the underlying tools...

For now I guess run sudo  btrfs check /dev/mapper/luks-* manually and see what it is complaining about.