NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
System volume root use is 95%, var/ftp is using it all
Hello, I have a ReadNas 102 and lately got these error messages that the system volume root use is 95%. After checking the /var folders I noticed that /var/ftp used all the space available. I had...
Hi.
The ibdata1 always growing is not a ReadyNAS problem, but a MySQL problem, maybe triggered or made worse by LogAnalyzer way to commit queries.
There is plenty of talk online about it. But it seems that there is no easy solution to reducing its size.
One example of thread: http://stackoverflow.com/questions/3456159/how-to-shrink-purge-ibdata1-file-in-mysql
If you don't use it, I suggest removing LogAnalyzer and mysql-server.
If you want to account what's actually in the OS volume:
# go to root cd / # count space usage per folder (only in the same filesystem) du -d1 -hx . # go to the biggest folder cd blablabla # repeat the operation du -d1 -hx . # once you're in the folder that contains the big files ls -alh
jak0lantash wrote:
If you want to account what's actually in the OS volume:
# go to root cd / # count space usage per folder (only in the same filesystem) du -d1 -hx . # go to the biggest folder cd blablabla # repeat the operation du -d1 -hx . # once you're in the folder that contains the big files ls -alh
du -d1 -hx . works in /var/ftp but the rest won't work unless you unmount the btrfs subvolumes correct? The cd will just take you into the data volume.
If the space really is in /var/ftp, then it was something written at startup before the data volume. That has sometimes happened. Support is of course one option.
The -x flag is to account for data only in the current filesystem. The data volume being another one, it's not accounted for.
If you really have data into a folder and mounted something on top of it, so I guess you won't be able to account for it this way (because of the cd).
But I'm presuming, the /var/ftp is not the culprit. It was just taken as is by mistake.
The user should do proper accounting with -x flag to make sure.
If you don't want to cd, you can still
# start with root du -d1 -hx / # go to biggest folder du -d1 -hx /foo # and so on # to finish with ls -alh /foo/bar
jak0lantash wrote:
The -x flag is to account for data only in the current filesystem. The data volume being another one, it's not accounted for.
On my NAS, using the -x flag in /var/ftp gives me 0 in all folders. Of course there is nothing in those mount points, and I have no way to put something in there with the NAS running, (and I don't know if I could use it to tell if something were stored in mount points).
I tested it on a Linux machine, once something is mounted on the mount point, you can't account for what was in it (until it's unmounted).
If JanvdBrink does a quick check of the OS volume using du, we'll quickly see if there is no other location with data.
If it's under /var/ftp and there is nothing mounted onto it, then we'll see it.
If it's under /var/ftp and there something mounted onto it, then we won't see it, but it seems unlikely that it was unmounted, and now mounted again.
If it's somewhere else than /var/ftp, then we'll see it ;)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
