From: Pierre C <lists@peufeu.com>
To: pgsql-performance@postgresql.org, "Ireneusz Pluta" <ipluta@wp.pl>
Subject: Re: Background fsck
Date: Mon, 18 Apr 2011 23:21:56 +0200
Message-ID: <op.vt5kaupmeorkce@apollo13> (raw)
In-Reply-To: <4D9EF6E3.9010402@wp.pl>
References: <4D9CEA3F.5050603@wp.pl>
<201104071701.02647.achill@matrix.gatewaynet.com>
<4D9EA367.7060102@wp.pl>
<201104080919.43152.achill@matrix.gatewaynet.com>
<BANLkTimoxYwhaL8zMXdswxnzHm2t13iY6Q@mail.gmail.com>
<4D9EF6E3.9010402@wp.pl>
> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: lists@peufeu.com, ipluta@wp.pl
Subject: Re: Background fsck
In-Reply-To: <op.vt5kaupmeorkce@apollo13>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox