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

Cleanup/update LVM size calculations and expectations #31

Closed
vpodzime opened this issue Mar 2, 2015 · 3 comments
Closed

Cleanup/update LVM size calculations and expectations #31

vpodzime opened this issue Mar 2, 2015 · 3 comments
Assignees

Comments

@vpodzime
Copy link
Contributor

vpodzime commented Mar 2, 2015

Blivet's LVM code contains many (often magic) calculations focused on free space left or required by LVM (e.g. "How much space is this LV going to take from a disk?" or "How much space there will be for LVM on top of RAIDn?"). Many of these calculations come from the lvm1 (called simply lvm) era and many are based on some empirical testing or just experience without any clear inspectable explanation. Also lvm2 has different size limitations than lvm1 used to have so we need to update these pieces of code/numbers too.

@vpodzime vpodzime self-assigned this Mar 2, 2015
@bcl
Copy link
Contributor

bcl commented Mar 2, 2015

Ideally this information would be provided by lvm in some way that doesn't require reading its code.

@vpodzime
Copy link
Contributor Author

vpodzime commented Mar 2, 2015

I think we all dream this dream. But I think (and even more I hope) there are many needless calculations in Blivet that origin from some noise and misunderstandings.

@vpodzime
Copy link
Contributor Author

Done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants