A restore from backup ought to keep the sparse volumes
Bug #2007615 reported by
Pete Zaitcev
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Fix Released
|
Medium
|
Pete Zaitcev | ||
Bug Description
At some installations, a significant fraction of volumes is sparse. If such a cluster has to be restored in a disaster recovery, it may not be possible to restore into the exact same equipment that was in the datacenter originally. As Cinder restores, it unrolls backup images with no regard to sparseness, and thus uses more space than was used at the time of backup.
Note that the backup saves the volumes correctly, preserving sparseness as compressed zeroes. The loss of sparseness occurs during the restore process.
| Changed in cinder: | |
| assignee: | nobody → Pete Zaitcev (zaitcev) |
| Changed in cinder: | |
| status: | New → In Progress |
| Changed in cinder: | |
| importance: | Undecided → Medium |
| tags: | added: backup-service |
To post a comment you must log in.

Red Hat had a bug about literally the same issue that was open back in 2020: /bugzilla. redhat. com/show_ bug.cgi? id=1855709
https:/