-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UUIDs not shown #21
Comments
I can't reproduce the problem on my side with just the info you gave, I do have the UUIDs on my output with the command you're typing. Maybe this has to do with the
|
|
I can reproduce it with btrfs-progs v6.1, which was broken for uuids, as seen by the fixing commit kdave/btrfs-progs@b7e3acd |
Tested all the released versions upstream, v6.1 seems the only one to have the problem, at least that I can reproduce.
If you don't see uuids there, it means that your version is somehow affected too (6.6.3-1.1build2, unsure if you compiled it yourself or if it's from a distrib) |
So... pebkac I didn't have any subvolumes, which is probably why subvolume uuids weren't shown. I created one and its shown:
However, this points out an indentation issue, the parentuuid dash (-) on the last row is one space too far right. Also I wonder if the original the original issue is more than a misunderstanding. |
About the indentation issue, can you try the latest (unreleased) version from the main branch? I fixed it yesterday (#19) but wanted to wait for this issue to be closed/solved before formally releasing a new version. If you can confirm that the current main branch fixes the indentation issue you have, that would be good! About the UUID of the main filesystem, I suppose I could add it in the UUID column if present indeed, even if the column was intended for subvolumes UUID at first, I suppose it doesn't hurt (parentuuid and rcvd_uuid will obviously stay empty however) |
I checked out the latest version and the indentation is fixed, great! |
UUIDs are not shown.
versus
The text was updated successfully, but these errors were encountered: