SUMMARY2: Solaris 2.3 panic ufs_ifree

V. Q. Hoang (vqh@dwrock.dw.lucent.com)
Wed, 05 Nov 1997 07:41:13 -0700

I got some more info on the issue, Bill Proud said that upgrading to
2.5.1 won't do any good. Bill sees the same thing on his fully patched
netnews server. John Di Marco said that he ran into the same
problem and the cause turned out to be a disk drive that couldn't
handle SCSI command tag queuing right so the filesystem gets corrupted
but there were no SCSI error messages recorded. We'll turn off
command tag queueing to see if it'll help.

> >
> > Thanks to Bismark Espinoza and Joel Lee for helping out.
> > It doesn't look like there's a fix for this problem.
> > We've discussed it with our customers and agreed to
> > upgrade to 2.5.1 in the hope that it has better ufs code.
> >
> > Viet Hoang wrote:
> > >
> > > We have a Solaris 2.3 system with a filesystem used for an application
> > > that
> > > creates a lot of little files. This filesystem was newfs'ed with -i
> > > 1024
> > > to twice more files than usual. Once every few months, this filesystem
> > > will cause the box to crash with PANIC: ufs_ifree: freeing free inode
> > > ....
> > >
> > > I've searched the sun-managers archive and sunsolve and I've seen many
> > > reports
> > > of this problem but I didn't see any fixes. Are there any? I'm
> > > considering
> > > upgrading to 2.5.1 but I recalled similar problems with early 2.5.1 too.
> > > Are there fixes for this problem in 2.5.1?

-- 


Viet Hoang
Lucent Technologies/IBM-GS
vhoang@lucent.com