Date: Sat, 9 Dec 2000 03:14:31 +0200 From: Tomi Vainio - Sun Finland - <Tomi.Vainio@Sun.COM> To: Mike Smith <msmith@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG Subject: Re: ffs_valloc: dup alloc panics with stable/current Message-ID: <14897.34679.98975.812334@ultrahot.Finland.Sun.COM> In-Reply-To: <200012090044.eB90i9F03062@mass.osd.bsdi.com> References: <14897.28646.3200.459030@ultrahot.Finland.Sun.COM> <200012090044.eB90i9F03062@mass.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Smith writes: > > First motherboard we tried was Intel PPro 200Mhz (FX440 based I > > think/Natoma?). Second one is newer 633MHz Celeron system but I don't > > know manufacturer. > > But the same symptoms? Have you tried replacing the controller (or even > just the onboard RAM)? > All but raid controller was replaced (RAM, video, net). We also have another raid controller and we are going to test it also. Also tried with and without soft updates and async io. > > But no other errors? In particular, nothing that looks like a "real" I/O > error? > This we have to double check because normally we don't stare at the console when we test this system. > The problem that you're seeing looks like filesystem metadata corruption. > If it's not memory/system related, it has to be in the datapath from the > disks through the driver. I'm not aware of any bugs in the driver that > could cause this. 8( > I think old PPro system even supported ECC memory. We are getting out ideas. Maybe small 3 disk raid5 with little newer disks than we use now. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14897.34679.98975.812334>