| From: | Tomasz Ostrowski <tometzky(at)batory(dot)org(dot)pl> |
|---|---|
| To: | Matthias(dot)Pitzl(at)izb(dot)de |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Strange database corruption with PostgreSQL 7.4.x o |
| Date: | 2006-09-20 14:20:46 |
| Message-ID: | 20060920142046.GH30944@batory.org.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 20 Sep 2006, Matthias(dot)Pitzl(at)izb(dot)de wrote:
> Any ideas how i could check the hardware?
1. memtest86 or memtest86+ at least 8 hours
2. CPU Burn-in
http://users.bigpond.net.au/cpuburn/ at least 8 hours
3. badblocks -s -v -t random /dev/sd%
WARNING: this will destroy your data!
4. smartctl -a /dev/sd%
Does not have to work. Sometimes needs some hacking to make it work.
Dave "KernelSlacker" Jones wrote a very good article about hardware
problems:
http://people.redhat.com/davej/hardware-problems.txt
Regards
Tometzky
--
...although Eating Honey was a very good thing to do, there was a
moment just before you began to eat it which was better than when you
were...
Winnie the Pooh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-20 14:31:35 | Re: Strange database corruption with PostgreSQL 7.4.x on Debian Sarge |
| Previous Message | Harry Hehl | 2006-09-20 14:17:14 | pg_dump output containing CREATE TYPE does not restore with psql |