kern/133980: panic: ffs_valloc: dup alloc

John Kilburg john at physics.unlv.edu
Fri May 8 01:30:06 UTC 2009


The following reply was made to PR kern/133980; it has been noted by GNATS.

From: John Kilburg <john at physics.unlv.edu>
To: bug-followup at freebsd.org
Cc:  
Subject: Re: kern/133980: panic: ffs_valloc: dup alloc
Date: Thu, 07 May 2009 18:28:38 -0700

 I am guessing now that this is a problem that I've seen mentioned
 in passing as a possibility in a few postings about the maximum
 number of inodes for UFS2.
 
 Using the default settings the filesystem ended up with more than
 2^31 inodes.  I decreased the inode density to about half the
 default (~1.4M inodes) and now things seem to be working perfectly.
 I rsync'd with 3 sessions, did a make buildworld and otherwise
 loaded the thing with no problems at all.
 
 It would be nice if newfs (or something) warned people about the
 effective 2^31 inode limit for ufs2 until the problem is spotted.
 I guess the real fix is to switch to a filesystem that doesn't
 have static inode allocation. :)
 
 							-john


More information about the freebsd-bugs mailing list