May 20, 20206 yr Not sure if my cache problem is related to overhead on raid0 configuration or something else entirely. I have a raid0 configuration of 3 small 32gb SSDs which should yield 96GB cache pool which it does but the drive shows 18GB used. My appdata folder is only 4.4GB and is currently the only thing on the cache drive? What could possibly be using 14GB of information that wouldn't be shown in the drive? (there are no hidden files that I missed). Wondering if I should recreate the cache array? Edited May 23, 20206 yr by coolasice1999
May 20, 20206 yr Community Expert du isn't reliable with btrfs, df (and the GUI) will show correct used space.
May 20, 20206 yr Author 21 minutes ago, johnnie.black said: du isn't reliable with btrfs, df (and the GUI) will show correct used space. Okay but I only have 4 gigs of data on there how do I find out what else is using all the space? Even Windows tells me there's only 4 gigs of data on there.
May 20, 20206 yr Community Expert Something is using it, Windows can also report wrong used space over SMB, move the data to the array and check again.
May 20, 20206 yr Author 4 minutes ago, johnnie.black said: Something is using it, Windows can also report wrong used space over SMB, move the data to the array and check again. not sure how that's possible when the only folder on the cache drive is the appdata folder. Guess I'll have to run a backup tonight and do a restore on that one.
May 20, 20206 yr Community Expert Move the appdata to the array and check the used space reported after that.
May 20, 20206 yr Community Expert If it's close to 0 after that appdata is using more space than you think, if not there's something else on cache.
May 20, 20206 yr Author 8 minutes ago, johnnie.black said: Move the appdata to the array and check the used space reported after that. That's the plan for tonight after work as the array is currently in use.
May 21, 20206 yr Author moving appdata didn't fix it... but i did find that shutting down the array caused it to freeze and after a hard reboot it fixed itself.
Archived
This topic is now archived and is closed to further replies.