Subject: Re: Problems with NetBSD 1.3 Solaris2 original filesystem
To: Manuel Bouyer <firstname.lastname@example.org>
From: Brian Buhrow <email@example.com>
Date: 01/07/1998 10:55:05
Hello Manuel. I threw in the towell and newfsed up a new filesystem.
Since we had been having problems with filesystem coruption under Solaris,
I thought perhaps there was some lurking under the covers that was biting
us. For some reason, I thought SCSIVERBOSE was turned on in generic
kernels, but I believe the problem may be taht we're trying to read beyond
the end of the disk. Do you know of a problem whereby Seagate disks report
more sectors than they actually have? This is a ST19171N. For good
measure, I reduced the cylinder count by a couplle and re-labeled the disk
before I newfsed. Is there a case where data corruption on the disk could
cause the system to try and read beyond the end of the filesystem? Also,
does NetBSD/Sparc know how to detect hardware errors, i.e. parity errors in
the same way SunOS and Solaris do on Sun equipment? My thought here is
taht there may have been some memory error which went undetected and which
caused faulty data to be written to disk at some point.
On Jan 7, 10:21am, Manuel Bouyer wrote:
} Subject: Re: Problems with NetBSD 1.3 Solaris2 original filesystem
} On Jan 6, Brian Buhrow wrote
} > Now, after having changed the CPU and the RAM, we're still seeing a
} > similar problem whereby the machine panics due to a kernel data fault.
} > However, we're also seeing a new type of panic on a 8GB filesystem which
} > was originally created under Solaris 2.5. Could someone explain what the
} > following message means, and if there is a way to fix it short of newfsing
} > the entire disk? Also, could this message, in some way, be causing the
} > kernel data faults as well?
} > [...]
} > login: sd4(esp2:3:0): illegal request, data = 00 00 00 00 21 00 03 cf 00 02
} > panic: ifree: range: dev = 0x722, ino = -254910704, fs = /var/spool/news
} > [...]
} The 2 panic messages can have the same cause. The ifree panic could also be
} caused by memory corruption.
} However, the "illegal request" message needs further sudies. Could you
} recompile a kernel with "options SCSIVERBOSE" so that we can have more details
} about the error ? Also the output of "df -ik" could be usefull.
} Do you have any swap space on this disk ?
} This disk is a news spool, rigth ? what is the size of your history file ?
} Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr
>-- End of excerpt from Manuel Bouyer