[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: free space problem
From:       Matthew Dillon <dillon () apollo ! backplane ! com>
Date:       1999-08-31 17:30:50
[Download RAW message or body]


:Hello,
:
:I am using 3.2-Stable and I have a 9GB disk drive used as cache for
:squid proxy. I have changed the min free space with tunefs program to 0
:but now I have a problem. Even though I have 250MB free space on the
:file system, I get file system full error.
:
:usr/local/squid/cache/disk1: write failed, file system is full
:cp: ./backup.28-08-1999.tgz: No space left on device

    You may have run out of inodes.

    Do a 'df -i'


    If this is the case you will have to newfs the filesystem again,
    this time using the -i option to change the inode ratio.

    Use df -i to see where you are now.

    Take the system offline.

    Make sure you have saved whatever data you need to save from the
    squid cache(s)

    unmount the filesystem(s)

    newfs them using varying values for the inode ratio.  The smaller the
    value, the more inodes you will have.   For example:

    newfs -i 8192 (thefilesystem)
    newfs -i 6144 (thefilesystem)
    newfs -i 4096 (thefilesystem)

    newfs will tell you how many inodes/cyl which you multiply by the
    number of cylinders to get the total.  Find a value for -i that matches 
    what you believe is appropriate for the filesystem based on your
    previous experience.

    You can also mount the filesystem and 'df -i' to see how many inodes
    you created.  Then unmount it and newfs with a different value and
    see how that works.  Etc...

    Be careful not to accidently newfs an active filesystem!

					    -Matt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message

[prev in list] [next in list] [prev in thread] [next in thread]