Forum Discussion

Tutor

Sep 03, 2020

Solved

Incorrect Consumed Storage

Hey guys, I hope everyone is keeping well!

For some odd reason, there’s a share that is reporting an incorrect “consumed” amount in the local GUI of the NAS. The value returned is: “16777216TB” of consumed space!?... (There is only 304MB of files.) The PC is simply connected to the share via drive mapping.

I’ve destroyed the snapshots for that share, defragged, scrubbed and balanced the system. (RAID 1) at this point not too sure what to do.

Has anyone ever come across this before, have any suggestions or should I just leave it be?

I’ve attached a highlighted screenshot.

Cheers

StephenB
Sep 03, 2020
Try creating a temporary share, and use a backup job to copy the contents. If that shows the correct size, you can delete the original share, and rename the temporary one to match the original's name.

3 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Sep 03, 2020
Try creating a temporary share, and use a backup job to copy the contents. If that shows the correct size, you can delete the original share, and rename the temporary one to match the original's name.
- new11
  Tutor
  Sep 04, 2020
  Hi StephenB,
  Thanks for the suggestion, I suppose I should have said in my OP that I'm a little more curious as to why the system may be displaying this value, I was thinking of that but thaught i'd see if anyone had experenced it before. Thanks all the same. :)
  Cheers
  - StephenB
    Guru - Experienced User
    Sep 04, 2020
    new11 wrote:
    
    I suppose I should have said in my OP that I'm a little more curious as to why the system may be displaying this value,
    
    I get that. I have seen this posted a couple of times before, but I don't know the cause. The number happens to be 2**64 bytes (1 EiB). That is the largest possible size of a BTRFS volume.
    
    My concern is that this might not be benign. Something isn't quite right with your btrfs on-disk structures for that subvolume (i.e. share), and that could cause problems for you later on. So if it were my system I'd be working to fix it, using the method I outlined above.