Changes between Initial Version and Version 1 of Ticket #15582, comment 2
- Timestamp:
- Jul 8, 2016 3:08:13 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15582, comment 2
initial v1 2 2 3 3 BEFORE: 4 {{{ 4 5 # VBoxManage showhdinfo /mnt/ssd-vm/virtualbox/Machines/win7-ordi/win7-ordi.vdi 5 6 UUID: d91d7251-dc2d-44b1-bb4f-5f1a8ac1c80a … … 21 22 -rw------- 1 avh avh 22K Jul 8 12:13 win7-ordi.vbox-prev 22 23 -rw------- 1 avh avh 31G Jul 8 12:31 win7-ordi.vdi 23 24 }}} 24 25 CMD: 26 {{{ 25 27 # VBoxManage modifymedium disk /mnt/ssd-vm/virtualbox/Machines/win7-ordi/win7-ordi.vdi --resize 44000 26 28 … … 31 33 VBoxManage: error: Code VBOX_E_FILE_ERROR (0x80BB0004) - File not accessible or erroneous file contents (extended info not available) 32 34 VBoxManage: error: Context: "RTEXITCODE handleModifyMedium(HandlerArg*)" at line 701 of file VBoxManageDisk.cpp 33 35 }}} 34 36 35 37 AFTER: 38 {{{ 36 39 # VBoxManage showhdinfo /mnt/ssd-vm/virtualbox/Machines/win7-ordi/win7-ordi.vdi 37 40 UUID: d91d7251-dc2d-44b1-bb4f-5f1a8ac1c80a … … 61 64 KERNEL: 62 65 Linux <hostname> 4.6.0-0.bpo.1-amd64 #1 SMP Debian 4.6.1-1~bpo8+1 (2016-06-14) x86_64 GNU/Linux 63 64 PS: This was a vdi backup put in place after the previous failed attempt at resizing. The virtual machine started normally for a brief test run and shut down cleanly. Should I have issued a # fstrim -v /mnt/ssd-vm before resizing? 66 }}} 67 PS: This was a vdi backup put in place after the previous failed attempt at resizing. The virtual machine started normally for a brief test run and shut down cleanly. Should I have issued a 68 {{{ 69 # fstrim -v /mnt/ssd-vm before resizing? 70 }}} 65 71 66 72 Regards, Andreas
