| From: | "Pierre C" <lists(at)peufeu(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org, "Ireneusz Pluta" <ipluta(at)wp(dot)pl> |
| Subject: | Re: Background fsck |
| Date: | 2011-04-18 21:21:56 |
| Message-ID: | op.vt5kaupmeorkce@apollo13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> What's more, this is already a new controller. It replaced the previous
> one because of exactly the same persisting problem. I think tech support
> people not knowing a solution just buy some time for them and say "flash
> this beta firmware maybe it helps" or "replace your hardware".
We had a problem like this on a server a few years ago on the job... The
machine randomly crashed once a month. XFS coped alright until, one day,
it threw the towel, and the poor maintenance guys needed to run xfsrepair.
Needless to say, the machine crashed again while xfsrepair was running
concurrently on all filesystems. All filesystems were then completely
trashed... That convinced the boss maybe something was wrong and a new box
was rushed in... Then a few tens of terabytes of backup restoration ...
zzzzzz ....
It turned out it was a faulty SCSI cable.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Keller | 2011-04-18 22:08:38 | How to configure a read-only database server? |
| Previous Message | Tom Lane | 2011-04-18 19:41:19 | Re: Assessing performance of fetches |