juju storage creates partition table, complicating expansion
Bug #1831965 reported by
Paul Collins
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
It seems that Juju's storage facility creates a partition table on the block device, and then creates the filesystem on that partition. This makes expanding volumes more complex than necessary.
Furthermore, on a cloud where block devices can be expanded online, it forces the filesystem to be unmounted so that the partition table can be re-read by the kernel following volume expansion, causing unnecessary downtime.
| description: | updated |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| status: | Triaged → Incomplete |
Revision history for this message
| Paul Collins (pjdc) wrote | #2 |
| Changed in juju: | |
| status: | Incomplete → New |
| tags: | added: storage |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| importance: | Wishlist → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
AFAIK, creating a partition table is done to limit the amount of space used to just that which was requested. Otherwise I thought the only other option is to consume the entire disk? Did you have a different implementation strategy in mind?