NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Free space reporting
1 TopicInaccurate reporting of used/free volume space
I have been moving all of my legacy equipment from OS 4.2.x to 6.4.2, so I have to factory default each of them with the new OS. As I do so, I've been making sure I have a new backup of data before destroying one of the existing two copies. That means I've been moving a lot of data on and off one system for temporary storage, and have recently filled it beyond the recommended limit. But while access got slowed as it got very full, that's the only performance issue I saw until now. I just deleted a very large amount of data, but did not delete the share that contained it nor any snapshots. When the volume was almost full (a bit more than 2% still avaliable, but that's still over 350MB reported free), came the first issue. Trying to add more files, either via Windows drag-and-drop or a ReadyNAS backup, failed due to being "out of space". Well, how can it be out of space and still report 350GB available on both the Share and Volume pages? If it's not really available, it should not be reported as available. Then, after I deleted that significant mass of files, the available space barely changed. I rather expected that because of the snapshots. But instead of the Shares page indicating most of it was used by snapshots, it indicated it was active storage. The totals of the shares' "Consumed" space was far less than the total "Data" space shown on the Shares and Volume pages, and Windows shows those consumed space numbers to be accurate. The available space reported in Frontview agrees with a DF command from SSH, but I don't know how to differentiate snapshot vs active space in SSH. I suppose this could be a BTFRS issue, not a ReadyNAS-unique one. Unfortunately, I didn't think to go to SSH when I was "out of space". So, I could have deleted the snapshots and see what happened as I did, but I decided to start another backup instead. Now will come the real test -- will the system delete snapshots and make the space available, as it should, or will it still say I'm out of space? Currently, the available space continues to drop, and has dropped below where it "ran out" before without failing. Stay tuned for reports on what happens next, and any suggestions as to what to try are welcome. If it's a bug, what can I do to help pin it down? If this is simply "the nature of the beast", it would be nice to characterize that nature so as not to get bitten too often. While this is happening on a legacy Pro6 system with 6.4.2, I don't see why it would be unique to that.Solved5.3KViews0likes7Comments
