NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Freeing up space on the OS partition (RAIDar 4.2.28, ReadyNAS Ultra 2)
From time to time (very rarely) my OS partition fills up to 100% causing all kinds of issues. Usually, the reason are some log-files that just became too big or too many. Once I had to move the CrashPlan cache to another partition. Once I cleared out stuff, the partiction usage was down to 30-40 percent again. But this time, I seem to be stuck at just under 80% and I can't figure out where all that junk might be . Or alternatively, why I suddenly need so much more space.
The problem is, I'm not a linux expert and I don't know exactly which directories are actually located on the OS partition. So far I have checked the following:
/var
/usr
/etc
/tmp
And I cleared all logs and obviously unnecessary files, but that doesn't seem to be enough.
What might I be missing?
Christoph
So every time I find myself trying to figure out, which directories are actually on the OS partition so that I can target these (obviously, I'm not a linux/debian expert).
Okay, so thanks to mdgm's assistance, it turns out that the files that were clogging up the OS partition were in /mnt/NAS2 where I had mounted another volume and to which Crashplan was writing its backup archives. The problem was that for mysterious reasons that volume disappeared from /etc/fstab and was no longer mounted. And as a result, Crashplan was writing to /mnt/NAS2 as a directory in the OS partition. I would never have thought that it is possible to write to /mnt/NAS2 when the volume is not mounted but apparently it is just an ordinary directory in those conditions.
In order to prevent that in the future, I am now mounting that external volume under the data partition instead of the OS partition,
8 Replies
Replies have been turned off for this discussion
I'd look in frontview and its subfolders next.
If you enter
cd //
ls -al
Then any folder that has a -> /c/... is a link to the data volume and can be ignored. You can also ignore c
You can use e.g. the du command to see how much is used by a directory.
For example I may use commands such as
# du -csh /var# du -csh /var/log/*
Most things under /var are on the root partition but if you have ftp enabled then the mounts under /var/ftp will be pointing to the data volume.
The locations you mentioned are the main ones to look at. Usually, but not always the culprit would be under one of those.
Aah, I should have guessed that everything that is nt /c/ would be the OS partition. Now I know. Thanks StephenB.
frontview is only 14 MB.
Will keep looking, but maybe that's just how much space the OS needs. Though I do seem to remember that it was much less last time I checked.
mdgm, yes, I have used du quite a bit, but du -h --max-depth=1
just gives me
16K ./lost+found 20K ./home 1.9T ./mnt 524K ./dev 0 ./sys
And then it becomes unresponsive and doesn't complete properly.
The root usage shouldn't really get above 30 to 40%. The 4GB of space is way more than enough.
Keep looking.Don't look at /dev /proc /sys or /run
The problem won't be in one of those directories. It will be in one of the others.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
