NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Out of memory isra 13+31c and RNDP4000 Lock up after upgrade to OS6 from OS4
after an initial successful upgrade from OS 4 to 6.1 and 4 x 8TB drives we've begun to experience access issues with our Readynas Pro 4 (RN). The error is repeatable as per the five steps outlined be...
Have you considered upgrading the memory on the Pro?
You shouldn't stick on old beta firmware.
Update to 6.7.1 and then perhaps disable quotas on the volume.
thanks for your suggestion.
we're a little hesitant about upgrading to 6.7.1 due to not being able to downgrade, the numerous posts
of other users under 6.7.1 having lockups and our own experience of the 6.6.1 to 6.6.1 t230 upgrade
failing to solve our issue, but having read this, we looked at the metadata setting under our own
btrfs.log and low and behold we too have a huge amount of metadata.
=== filesystem /data ===
Data, single: total=10.59TiB, used=10.50TiB
System, DUP: total=8.00MiB, used=1.12MiB
Metadata, DUP: total=5.50GiB, used=4.55GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
with a very simplistic understanding of the RN's mechanics it seems completely plausible to link
oversized metadata content with the out of memory messages we've been getting so perhaps there's
hope yet! we understand that we'd need to use SSH and # btrfs quota disable /data to disable quotas
but is there any way (without having to carry out a third factory reset) to reduce the current size of
our metadata or is it only through carrying out the steps of
1. a factory reset
2. disabling quotas and then
3. restoring fresh a backup
the only way to keep the metadata size down?
For the amount of data you have the amount of metadata you have is quite reasonable.
Disabling/enabling quotas would have minimal effect on the amount of metadata. Presumably quotas would be stored in metadata, but it doesn't take much space to store a few numbers.
metadata is data about data. Lots of CoW (Copy on Write) leads to a lot of metadata.
6.7.1 has a GUI option to disable quotas on the volume.
Disabling quotas on the volume is a good troubleshooting step. If that doesn't resolve it then there are others reasons for OOMing that could be considered. If you review the logs you should see which processes were using lots of memory when it OOMed.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
