Bug #2426
Volatile disks changes from sparse to real on migrate (using ssh tm)
| Status: | Closed | Start date: | 11/04/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Javi Fontan | % Done: | 0% | |
| Category: | Drivers - Storage | |||
| Target version: | Release 4.4 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.2 |
Description
Volatile disks are created as sparse files and usually takes not much space. But on cold migration with ssh transfer manager all sparse files become real ones. As a side effect, copying process takes much longer because of reading virtual segments too.
Associated revisions
bug #2426: handle sparse images in tm ssh mv (tar)
(cherry picked from commit 0c88cde992f834760096a90bef279c0db50824e7)
bug #2426: handle sparse images in tm ssh mv (tar)
(cherry picked from commit 0c88cde992f834760096a90bef279c0db50824e7)
History
#1
Updated by Andrey Perminov over 7 years ago
All you need is to add --sparse (-S) key to tar command of migrate script.
#2
Updated by Ruben S. Montero over 7 years ago
- Status changed from Pending to New
- Assignee set to Javi Fontan
- Target version set to Release 4.4
- Affected Versions OpenNebula 4.2 added
Thanks for the feedback. Scheduling this for 4.4.
#3
Updated by Ruben S. Montero over 7 years ago
- Status changed from New to Closed
- Resolution set to fixed