[6.11.5] Used/free disk space incorrectly reported in GUI on Dashboard and Main tab

More info: after rebooting the GUI seems to "remember" the newer 7 gb file I added, as used space remained 35 gb. I should have mentioned that I swapped SATA ports during the reboot that caused the issue. I switched it back and the problem persisted, so I didn't think it was relevant.

This is not directly an Unraid problem since df reports the same:

 

Filesystem      Size  Used Avail Use% Mounted on
/dev/md1        3.7T   26G  3.7T   1% /mnt/disk1

 

Unraid doesn't use df, but probably gets the stats form the same place, so it's some issue with Linux and XFS, is it possible for you to try without hardlinks to see if you see the same?

5 hours ago, JorgeB said:

This is not directly an Unraid problem since df reports the same:

 

Filesystem      Size  Used Avail Use% Mounted on
/dev/md1        3.7T   26G  3.7T   1% /mnt/disk1

 

Unraid doesn't use df, but probably gets the stats form the same place, so it's some issue with Linux and XFS, is it possible for you to try without hardlinks to see if you see the same?

To do this - do I just turn off hardlinks in global drive settings? If I do that, when I turn it back on will hardlinks be in tact?

Not sure if just disabling now will change anything, also not sure if they would remain intact after re-enabling, ideally you would test with a different disk, or after starting over if that's possible.

Ok update: I tried setting the share to Cache: Prefer and having mover send everything back to the cache drive, in the hopes of then sending all the data back to the array and seeing if unraid would then "see" the data on it. Unfortunately the mover error'd out after one file and the array drive was then seeing as unmountable due to a filesystem error. I did xfs_repair on the drive and now it's seeing everything as normal, all files visible on the array drive and utilization is correct.

 

Do you think this is the sign of a bad drive or connector? What could have caused the file system error? Thanks.

@JorgeBI've attached diagnostics to this after the fix. Can you please confirm that the df output looks OK? Sorry I'm a noob.

 

wyse-diagnostics-20230404-2217.zip

Everything looks good so far, so likely and in this case, the original issue was just filesystem corruption.

5 hours ago, JorgeB said:

Everything looks good so far, so likely and in this case, the original issue was just filesystem corruption.

Thanks for your help!

Changed Status to Closed

Changed Priority to Other