| From: | Wim <wdh(at)belbone(dot)be> |
|---|---|
| To: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
| Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Still big problems with pg_dump! |
| Date: | 2002-09-17 14:56:26 |
| Message-ID: | 3D87429A.6090809@belbone.be |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general pgsql-hackers pgsql-novice |
Andrew Sullivan wrote:
>On Tue, Sep 17, 2002 at 04:46:00PM +0200, Wim wrote:
>
>
>>>That won't help you if the controller is coming and going; you might
>>>find that it works one time, and not another. Indeed, a disk on its
>>>way out can even pass fsck sometimes, although it's pretty unusual.
>>>
>>>
>>>
>>The DB is located on a RAID5 disk array...
>>
>>
>
>Hmm. _That's_ interesting. I'd bet on a flakey controller, then.
>Is it hardware RAID? (I assume so.)
>
>A
>
>
>
Yep, hardware RAID, infact it's a SUN T3 disk array with 9*36GB SCSI
disks...
Cheers!
Wim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2002-09-17 14:58:01 | Re: [GENERAL] Still big problems with pg_dump! |
| Previous Message | Tom Lane | 2002-09-17 14:55:18 | Re: [GENERAL] Still big problems with pg_dump! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2002-09-17 14:58:01 | Re: [GENERAL] Still big problems with pg_dump! |
| Previous Message | Tom Lane | 2002-09-17 14:55:18 | Re: [GENERAL] Still big problems with pg_dump! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2002-09-17 14:58:01 | Re: [GENERAL] Still big problems with pg_dump! |
| Previous Message | Tom Lane | 2002-09-17 14:55:18 | Re: [GENERAL] Still big problems with pg_dump! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2002-09-17 14:58:01 | Re: [GENERAL] Still big problems with pg_dump! |
| Previous Message | Tom Lane | 2002-09-17 14:55:18 | Re: [GENERAL] Still big problems with pg_dump! |