inn-2.3.1 causing filesystem problems

Russ Allbery rra at stanford.edu
Sat Aug 18 21:16:17 UTC 2001



Charles Clancy <mgrtcc at cs.rose-hulman.edu> writes:

> Configuration:
> - INN-2.3.1, fully tradspool
> - Sparc/Ultra 2 (2x200 MHz, 256M RAM)
> - Solaris 8, HW 10/00

> Observation:
> [news] [shiva]/var/news/tmp> df -v | grep news
> /newsdisk0 /dev/dsk/c0t1d0  6075693  2880197  3134740    48%
> /newsdisk1 /dev/dsk/c0t4d0  8719461  3388702  5243565    40%
> [news] [shiva]/var/news/tmp> touch file
> [news] [shiva]/var/news/tmp> ls
> file
> [news] [shiva]/var/news/tmp> /var/news/bin/rc.news start
> Starting innd.
> Scheduled start of /var/news/bin/innwatch.
> [news] [shiva]/var/news/tmp> touch file2
> touch: file2 cannot create
> [news] [shiva]/var/news/tmp> ps -ef | grep inn | awk '{print $2}' | xargs kill
> [news] [shiva]/var/news/tmp> touch file2
> [news] [shiva]/var/news/tmp> ls
> file   file2

> When inn is running, the OS is convinced that /newsdisk0 (/var/news is
> symlinked to /newsdiks0) is full and refuses to let me create files on
> it.  Have you ever seen this behavior before?  Is there any fix for the
> problem?

I don't know if you ever resolved this problem (the message is quite old),
but have you already checked to make sure that you're not out of inodes?
df -i will show you inode usage.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>


More information about the inn-bugs mailing list