November 1, 20169 yr I don't know what's wrong but my VM's all of a sudden keep pausing. Can anyone decipher anything from the logs? I've seen some posts where people suggest that running out of resources can cause this but that doesnt look like my issue unless i'm looking in the wrong place. My logs are attached thecouncil-diagnostics-20161031-2040.zip
November 2, 20169 yr Both your VMs are on disk23, and you're out of space: [idx] => 23 [name] => disk23 [device] => sdg [id] => INTEL_SSDSCKGW080A4_CVDA326101NQ080G [rotational] => 0 => 78150712 [status] => DISK_OK [temp] => 45 [numReads] => 1041390 [numWrites] => 439180 [numErrors] => 0 [format] => MBR: 4K-aligned [type] => Data [comment] => => green-on [exportable] => no [fsStatus] => Mounted [fsColor] => green-on [fsError] => [fsType] => xfs [fsSize] => 78112556 [fsFree] => 20 [spindownDelay] => -1 [spinupGroup] => host7 [deviceSb] => md23 [idSb] => INTEL_SSDSCKGW080A4_CVDA326101NQ080G [sizeSb] => 78150712
November 2, 20169 yr Author So do those images need room to grow? I guess that it was naive of me to not know that. Within the vm's there is free space inside of the virtual disk as seen by the OS. I guess that's not good enough? So can I just move the vdisk.img file to a different drive? (Thanks a ton for your assistance by the way.)
November 2, 20169 yr Vdisks are sparse, i.e., you can create a 100GB vdisk on a 80GB disk, the OS will see 100GB but when you reach 80GB it will be out of space despite the OS still seeing 20GB free.
November 2, 20169 yr Author I moved one of the VM's to the cache drive and deleted the old image. Lets see how it goes. I naively thought that creating two 40gb vm images on an 80gb drive would be fine. They ran perfectly for almost a year.
November 2, 20169 yr It would be fine if account for the byte/gigabyte difference in Windows, e.g.: Your SSD is 80 000 000 bytes = 76.29GB You'd be fine with 2 x 38GB vdisks, not fine with 2 x 40GB vdisks.
Archived
This topic is now archived and is closed to further replies.