Re: Serious Crash last Friday - Mailing list pgsql-general

Hi,

thanks for the information...

the badblocks read-only test did not report any problems,
do you think i should run the "read-write" test, too?

i did the last initdb 3 weeks ago and created every table new from dumps.
i am recreating all user-indexes every day, i am vacuuming everything
everyday.

the server has only been running for 4 months, it's brand new hardware
(Intel PIII,
900 MHz, 2 x 60 GB SCSI-Raid 0 disks) ... it has been up and running for 42
days
without reset now (last reset was due to work at powerswitch).

tonight I will have the memory checked by memtest86 ...


Mit freundlichem Gruß

Henrik Steffen
Geschäftsführer

top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684 Stade - Germany
--------------------------------------------------------
http://www.topconcepts.com          Tel. +49 4141 991230
mail: steffen@topconcepts.com       Fax. +49 4141 991233
--------------------------------------------------------
24h-Support Hotline:  +49 1908 34697 (EUR 1.86/Min,topc)
--------------------------------------------------------
System-Partner gesucht: http://www.franchise.city-map.de
--------------------------------------------------------
Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
--------------------------------------------------------

----- Original Message -----
From: "Andrew Sullivan" <andrew@libertyrms.info>
To: "pg" <pgsql-general@postgresql.org>
Sent: Wednesday, July 10, 2002 4:38 PM
Subject: Re: [GENERAL] Serious Crash last Friday


> On Wed, Jul 10, 2002 at 02:51:00PM +0200, Henrik Steffen wrote:
> > excuse me, but what is a "non-destructive badblocks (or
> > whatever) test" - and how can I do this?
>
> If you're using linux, try "man badblocks".
>
> On Solaris, a similar command is diskscan.
>
> Other systems will have other names.  I can't recall how to do this
> on BSD, and I can't find anything in my local man db at the moment.
> I'll bet someone else here knows.
>
> You should check for other hardware faults, too.  A bad memory module
> can provide for all sorts of strange errors on your system (although
> if it never locks up or crashes, I'd look elsewhere for the problem
> first).  In recent releases, PostgreSQL has proven to be very stable,
> but you are having a lot of trouble, and many others are not
> reporting similar problems.  That leads one to suspect that you have
> faulty hardware; it certainly requires, at least, that you eliminate
> hardware as a factor.
>
> A
>
> --
> ----
> Andrew Sullivan                               87 Mowat Avenue
> Liberty RMS                           Toronto, Ontario Canada
> <andrew@libertyrms.info>                              M6K 3E3
>                                          +1 416 646 3304 x110
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly