NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS 314 incorrect consumed storage reporting
I have been moving some large files around and have tried running a balance but something is incorrect about my storage reporting in FrontView. I have a ReadyNAS 314 running the latest firmware (...
whetsel wrote:
I may also try: (not sure /mnt is the correct location to run this against)
btrfs balance start /mnt
It's not. Normally mount is an empty folder in root.
No idea why the command did something to the data volume on Sandshark's system back in 2016.
whetsel wrote:
If this doesn't work, what the heck are my next steps?
Obviously it would be prudent to have an up-to-date back up of the data.
You should be using btrfs commands for your troubleshooting - the usual linux commands do not give the right answers for btrfs.
btrfs fi show /data btrfs fi df /dataYou can check if you deleted all the snapshots using this:
btrfs subvolume list -s /dataThis will also give more details
btrfs fi du -s /data/sharenameThis last command can take a long time to complete. You can leave off the -s, but you will get a lot of output.
Note also you can use it (with or without the -s) on subfolders of the share, or even individual files.
StephenB thanks for the replies.
I ran the btrfs commands you wrote out sans the one the last one, here were the results:
root@NAS:~# btrfs fi show /data
Label: '2fe61160:data' uuid: c85f4904-6807-44ea-9295-dffc33cd23be
Total devices 1 FS bytes used 13.85TiB
devid 1 size 16.36TiB used 16.02TiB path /dev/md127
root@NAS:~# btrfs fi df /data
Data, single: total=15.98TiB, used=13.84TiB
System, DUP: total=32.00MiB, used=2.25MiB
Metadata, DUP: total=15.50GiB, used=11.62GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
root@NAS:~# btrfs subvolume list -s /data
root@NAS:~#
The balance I started last night via SSH is still running this morning, but I am happy to report that having just log into FrontView it is now reporting correctly. I rushed the post last night in concern, but it appears a balance indeed fixes things. Not sure why the GUI balance did not vs the one I ran from SSH is working.
PS. Thanks for confirming that /mnt was the wrong location for the "full balance". I could not for the life of me think how that helped them, I was going to run it against /data but won't now.
whetsel wrote:
The balance I started last night via SSH is still running this morning, but I am happy to report that having just log into FrontView it is now reporting correctly. I rushed the post last night in concern, but it appears a balance indeed fixes things. Not sure why the GUI balance did not vs the one I ran from SSH is working.
There a balancing between speed of the balance and the amount of space reclaimed.
The GUI was probably using a higher threshold for -dusage, which wouldn't compact as many blocks.
You could try running balance a couple of times with successively smaller -dusage values - it likely will free up a bit more space. Best not to go to -dusage=0 in one step - that can take a very long time, and might also run out of working space for the compaction. Lowering it gradually usually results in each step completing quickly.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
