NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Retired_Member
Oct 09, 2015After update RN102 from 6.2.5 to 6.4.0 it sends mail with root usage 86%
I've updated my ReadyNAS and now i get mail notifications that the root usage is 86%. I think it isn't true beause the data storage has over 700GB free space and /dev/md0 has 2.4GB free space. What...
Retired_Member
Oct 09, 2015You are right. The inode usage is 86%.
Here the original message from df -i:
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/md0 65536 56246 9290 86% /
How can I fix it?
StephenB
Oct 09, 2015Guru - Experienced User
There must be some folder that has a bunch of small files (maybe even 0 length). Basically you need to search for it. /tmp, /var/log, /var/cache are good places to start.
With OS 4.2, that is usually the ReadyDLNA artwork cache. But with OS 6 that should be in /apps - which is on the C drive.
Once you find where the files are, it might be clear that they can safely deleted. If not, post back here.
Best to update your backup first - it is easy to make a fatal mistake with ssh.
Netgear can fix it remotely also - so you could try support.netgear.com. Even if you are past the 90 window, they might help w/o charge.
- Retired_MemberOct 10, 2015
I found many files in /var/backups. Recently I have made a backup of the configuration. I think this folder can be cleared?
I have also some mysql databases in /var/lib/mysql. I will transfer them to the hard disk drives.
Only these two folders are filled with many small files.
I try it and give a feedback here.
Thanks for your advices.
- StephenBOct 10, 2015Guru - Experienced User
I don't know how /var/backups is used - so I'm not sure if it is safe to clear or not.
Generally there is 1 inode per file. My RN202 has is using about 11000 inodes on the OS partition. So you are looking for about 40,000 files - not a handful.
- Retired_MemberOct 10, 2015
There is no effect by doing anything.
I (re)moved nearly 2000 files and the output of df -i is the same.
I guess the filesystem is corrupt but I don't know how to fix the root filesystem.
I tried shutdown -rF (Parameter F doesn't exist) and touch /forcefsck an reboot system. No effect.
The last checked property of "tune2fs -l /dev/md0" shows "Sat Oct 18 21:19:31 2014". :(
How can I force a fsck scan at the root partition?
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!