User Tools

Site Tools


faq:0046

Q: How do I fix errors like “pid 2352 (smbd), uid 21 inumber 3006 on /: filesystem full” that appear in the logs?
Q: Why is my / file system full?
A:
There are a few reasons why this happens. You should read this FAQ completely, determine why you are getting the error and then select the method to fix it that makes you happiest.

One common reason is accidental sharing of /mnt directory. /mnt is part of the root ( / ) file system and should never be shared! All shares should be created below /mnt, ( e.g., /mnt/YourStuff ). If you make this mistake, Windows will show the total size of the root file system ( / ), not your drive and your free space will equal that reported for /.

  • Samba puts its Recycle Bin in the root directory of the share. If you created a share with a path of /mnt or anywhere in the root ( / ), deleting files on any of your mounted drives will cause them to be moved into /mnt/.recycle, thus quickly overflowing the root file system.
  • AFP can also create invisible files on its shares that can help fill up the the root ( / ) file system.

These things can happen regardless of how you are running or have installed XigmaNAS if you have created shares above /mnt/.

Solution: Either do not share /mnt, and/or disable Samba Recycle Bin in WebGUI Tab> Services > CIFS/SMB > Shares.

Wait, I was smart, I didn't share /mnt or enable Recycle Bin, or AFP and I am not running a Nightly Build, but I am still getting file system full errors, why? Because some file has gotten so big that it's using up all the space on / or you've installed extensions / packages on “Embedded” or “Live USB” instead of using “Full”. This problem is most common when you run “Live CD” “Live USB” or “Embedded” platforms because they run from a small RAM disk, but you may also eventually run out of space, even with a “Full” install. It happens even though you are not deliberately saving data to /, because the system still uses / for various purposes. The most common cause is large log files created in /var/log. You can use FIND to determine what files are growing too large:

find / -type f -size +8192 -ls -xdev

Once you find it you can take steps to fix the problem.

Here are 4 typical solutions:

  1. Try using Full instead of Embedded or one of the Live installations. (This is the absolute least advised option, and if you use it, you are very unlikely to get support because full installs are universally advised against.)
  2. Change log file locations. There are a couple of different ways to do this. If only RSYNC_LOCAL.LOG is a problem you can move RSYNC_LOCAL.LOG alone.
    Probably the easiest way is to use WebGUI Tab> System > Advanced > rc.conf. Add a new Variable, Value (path to a directory that will not be overwritten on boot where you will store the files) and Description as follows:
    Variable: clog_logdir
    Value: /mnt/data/logs
    Description: Log files location. 
  3. Edit RC.CONF and increase the size of your RAM disk. You can also find info here on how to change other rc.conf parameters.
  4. Keep watching how full your / directory is and prune or delete files as needed. Some scripting and CRON can be helpful if you decide to use this option.

References:

Advanced Basic XigmaNAS Tune-up ⇒9.0.0.1
faq/0046.txt · Last modified: 2018/08/10 20:40 by zoon01