Skip to content
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

A script to test relation of AllocatedSize and TotalPhysicalUsed #283

Open
mulkieran opened this issue Apr 26, 2022 · 1 comment
Open

A script to test relation of AllocatedSize and TotalPhysicalUsed #283

mulkieran opened this issue Apr 26, 2022 · 1 comment
Assignees

Comments

@mulkieran
Copy link
Member

The difference between these should be the same as the difference between the thinpool data device's total size and it's total used value as obtained via devicemapper.

AllocatedSize and TotalPhysicalUsed should be obtained via the D-Bus but the thinpool data device information would probably have to be obtained via dmsetup.

@mulkieran mulkieran self-assigned this Sep 18, 2024
@mulkieran mulkieran added this to the Metadata-related milestone Sep 18, 2024
@mulkieran mulkieran removed this from 2024September Oct 7, 2024
@mulkieran mulkieran removed this from 2024October Nov 4, 2024
@mulkieran mulkieran moved this from Todo to In Progress (long term) in 2024November Dec 2, 2024
@mulkieran
Copy link
Member Author

We could do this internally, via an invariant.

@mulkieran mulkieran removed this from 2024November Dec 3, 2024
@mulkieran mulkieran moved this from Todo to In Progress (long term) in 2024December Dec 3, 2024
@mulkieran mulkieran removed this from 2024December Jan 6, 2025
@mulkieran mulkieran moved this from Todo to In Progress (long term) in 2025January Jan 6, 2025
@mulkieran mulkieran removed this from 2025January Feb 10, 2025
@mulkieran mulkieran moved this from Todo to In Progress (long term) in 2025February Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress (long term)
Development

No branches or pull requests

1 participant