Too many files crashing services

Robert Fitzpatrick robert at webtent.com
Mon Dec 5 15:25:56 PST 2005


On Mon, 2005-12-05 at 16:16 +1100, Norberto Meijome wrote:
> Norberto Meijome wrote:
> > 
> > No, you are running out of maxfiles, as per "kern.maxfiles limit 
> > exceeded by uid ..." .
> 
> errr... of course, i meant to say, you have more open files than allowed 
> by kern.maxfiles.

Well, I just did some fsck /var and get a few INCORRECT BLOCK COUNT in
Phase 1, lots of these in Phase 2:

UNALLOCATED  I=967619  OWNER=postfix MODE=100600
SIZE=353 MTIME=Dec  5 18:18 2005
FILE=/spool/postfix/defer/E/E60BEEC3C2

UNEXPECTED SOFT UPDATE INCONSISTENCY

REMOVE? no

And plenty of this in Phase 4:

UNREF FILE  I=22  OWNER=vscan MODE=100640
SIZE=80174 MTIME=Jun 20 11:30 2005
RECONNECT? no

So on and so on...could these things cause my 'Too many open files'
issues and reaching kern.maxfiles? And what are the risks of allowing
all these issues to 'REMOVE' and 'RECONNECT' in single user mode?

fsck /usr not as bad, but still:

esmtp# fsck /usr
** /dev/da0s1d (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT FILE I=2425895  OWNER=pgsql MODE=0
SIZE=0 MTIME=Dec  5 18:23 2005  COUNT 0 SHOULD BE -1
ADJUST? no

** Phase 5 - Check Cyl groups
SUMMARY INFORMATION BAD
SALVAGE? no

ALLOCATED FILE 2425895 MARKED FREE
ALLOCATED FRAG 9702124 MARKED FREE
BLK(S) MISSING IN BIT MAPS
SALVAGE? no

326108 files, 2473634 used, 7443685 free (128341 frags, 914418 blocks,
1.3% fragmentation)

--
Robert




More information about the freebsd-questions mailing list