Hello,

 

I've recently been getting cache drive low space warning messages and I'm trying to find out what is using the space so I can free it up.

Is there a preferred method or command to list folder sizes on mnt/cache? (I have no shares on it)

 

Thanks

All root folder will be shares, you can compute the used space on the Shares webpage.

Thanks Johnnie I've done that and I can see now mnt/cache has the following:

 

Appdata - 2.39GB

VM - 181GB

docker.img - 10.7GB

Libvirt.img - 1.07GB

=  195.16 GB

 

UNRAID is showing 237GB used 18GB free, I seem to be missing 40GB is there hidden folders maybe?

 

Edited May 29, 20179 yr by egtrev

If cache is btrfs used space calculation may be incorrectly reported by unRAID or du, you need to use:

 

btrfs fi df -H /mnt/cache

 

5 minutes ago, johnnie.black said:

If cache is btrfs used space calculation may be incorrectly reported by unRAID or du, you need to use:

 

btrfs fi df -H /mnt/cache

 

 

 

Thanks Johnnie - I get the follow from that command:

 

btrfs fi df -H /mnt/cache
Data, RAID1: total=254.95GB, used=238.13GB
System, RAID1: total=33.55MB, used=65.54kB
Metadata, RAID1: total=1.07GB, used=207.49MB
GlobalReserve, single: total=104.45MB, used=0.00B

 

Seems to show roughly the same

2 minutes ago, egtrev said:

used=238.13GB

 

That's the actual used space, so if:

52 minutes ago, egtrev said:

UNRAID is showing 237GB

 

it's correct

Yes, but as I mentioned I'm only using 197GB, trying to find the missing 40GB.

 

56 minutes ago, egtrev said:

Thanks Johnnie I've done that and I can see now mnt/cache has the following:

 

Appdata - 2.39GB

VM - 181GB

docker.img - 10.7GB

Libvirt.img - 1.07GB

=  195.16 GB

 

UNRAID is showing 237GB used 18GB free, I seem to be missing 40GB is there hidden folders maybe?

 

 

Like I said above, with btrfs the used space reported by the compute option in the shares page or du can be a little off (or a lot off if using snapshots or reflinks, nothing you can do about it, the total used space is correct as reported by unRAID and brtrfs fi df.

 

Most likely the sparse vdisk is the reason for the difference, if you're not already see here how to recover unused space from the vdisk so that it doesn't keep growing constantly:

 

 

On 29/05/2017 at 3:00 PM, johnnie.black said:

Most likely the sparse vdisk is the reason for the difference, if you're not already see here how to recover unused space from the vdisk so that it doesn't keep growing constantly:

 

Hi Johnnie, I only have one Windows VM, I've tried the guide but can't get it to boot after step one (adding scsi controller lines). I just see a black screen. Removing the scsi controller lines allows the VM to boot again. Only error I can see in the log:

 

qemu-system-x86_64: virtio_ioport_write: unexpected address 0xc value 0x0

 

No idea, did you copy past all the changes? A single digit error can be a problem.

2 hours ago, johnnie.black said:

No idea, did you copy past all the changes? A single digit error can be a problem.

 

Yes I copy/pasted from the guide and added:

<controller type='scsi' index='0' model='virtio-scsi'>
</controller><controller type='scsi' index='0' model='virtio-scsi'> </controller>

After this I can't get the VM to boot to proceed with the rest of the guide.

 

Below is the full XML after I update (the below XML won't boot)

 

<domain type='kvm'>
  <name>Windows 10</name>
  <uuid>7b905806-8a74-3d61-e5d7-423fbbb73842</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>6815744</memory>
  <currentMemory unit='KiB'>6815744</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='2'/>
    <vcpupin vcpu='2' cpuset='5'/>
    <vcpupin vcpu='3' cpuset='6'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='2' threads='2'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/VM/Windows 10/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/ISO/virtio-win-0.1.113-1.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <controller type='scsi' index='0' model='virtio-scsi'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:46:52:df'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

 

 

Sorry, no idea, you're the first to report that error with this.

9 hours ago, johnnie.black said:

Sorry, no idea, you're the first to report that error with this.

 

Before the guide it says:

"it's possible to "re-sparsify" the vdisk e.g., by coping it to another file, but this it's not very practical"

Should I try that way instead maybe? Is there a guide for this method?

Thanks for your help.

 

1 hour ago, egtrev said:

Is there a guide for this method?

 

That will work and it's very easy, but the file will start to grow again with time:

 

cp --sparse=always old_vdisk.img new_vdisk.img

 

Edited June 1, 20179 yr by johnnie.black

10 hours ago, johnnie.black said:

 

That will work and it's very easy, but the file will start to grow again with time:

 

cp --sparse=always old_vdisk.img new_vdisk.img

 

 

Thanks I'll try that.

Is there anyway to have the vdisk not sparse? eg if I allocate 80GB to a VM it always uses 80GB of space, no more, no less (providing there is enough space to start with) or is this a bad move?

20 minutes ago, egtrev said:

Is there anyway to have the vdisk not sparse?

 

AFAIK it's always created sparse, but you use cp to make it not sparse:

 

cp --sparse=never old_vdisk.img new_vdisk.img