Cache drive getting full but can't find the data

[Marzel]

Hello Community

 

I logged into my Unraid this morning and found that my cache drive is 71% full. When I tried to find out what data is on the disk, I only found 174GB. However, the SSD is 1TB large and there are 706GB occupied displayed.

 

 

Does anyone have a tip or an idea what could be going on?

 

Thanks already for your help!

Marzel

heimdall-diagnostics-20220921-0814.zip

[JorgeB]

If you have a Windows VM make sure the vdisk is being trimmed:

https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606

 

[Marzel]

14 minutes ago, JorgeB said:

If you have a Windows VM make sure the vdisk is being trimmed:

https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606

 

 

Thank you for your answer. If i get that right, it appliers only for Window VMs right? I just have one Ubuntu VM with a 50GB vdisk, so shouldn't be the problem right?

[JorgeB]

It could if it's not being trimmed, but not sure how to do that for Ubuntu VM, you could move the vdisk to the array temporarily to see if that is the problem., if it isn't start moving the other stuff, something is using that space, could be due to fragmented extents.

[Marzel]

I already started moving the VM to the array, let's see if that makes a differentes.

 

Again Thanks for you help!

Edited September 21, 2022 by Marzel

[Marzel]

Even after I emptied the cache drive, 1.7GB are supposedly still occupied. Most of the "700GB" was the appdata folder, which is still 11.5GB in the array.

 

 

I honestly don't understand what is going on here.

[JonathanM]

7 minutes ago, Marzel said:

Even after I emptied the cache drive, 1.7GB are supposedly still occupied.

File system overhead.

 

[Marzel]

That explains it, after a reboot it's now just 3.82MB. I will now move the files and folder back to cache and hope that the disk show the used space correctly.

[JorgeB]

Copy the vdisk with

cp --sparse=always /source /dest

This will make it as small as possible, though it will grow with time if it's not trimmed.

[trurl]

Why do you have 100G docker.img? That is several times too large. 20G is often more than enough. Have you had problems filling it?

[Marzel]

After copying everything back it's now showing 141GB used. So your cp command @JorgeB did shrink the vdisk also, thank you for that.

 

1 hour ago, trurl said:

Why do you have 100G docker.img? That is several times too large. 20G is often more than enough. Have you had problems filling it?

Yes I have reached the 20GB limit. Because of that i extended the docker.img and i have the disk space(1TB) so i thought, i will go with 100GB. But now it only uses 23GB of the 100GB.

[JorgeB]

Docker image can also grow with time, use only what you really need.