Re: Postgres, fsync and RAID controller with 100M of internal cache & dedicated battery

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: dmitry(at)koterov(dot)ru
Cc: "Postgres General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgres, fsync and RAID controller with 100M of internal cache & dedicated battery
Date: 2007-08-22 15:47:25
Message-ID: dcc563d10708220847ydc2e90dk8d7e98462fc99c22@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/22/07, Dmitry Koterov <dmitry(at)koterov(dot)ru> wrote:
> Hello.
> You see, 50M block was fsynced for 0.25 s.
>
> The question is: how to solve this problem and make fsync run with no delay.
> Seems to me that controller's internal write cache is not used (strange,
> because all configuration options are fine), but how to check it? Or, maybe,
> there is another side-effect?

I would suggest that either the controller is NOT configured fine, OR
there's some bug in how the OS is interacting with it.

What options are there for this RAID controller, and what are they set
to? Specifically, the writeback / writethru type options for the
cache, and it might be if it doesn't preoprly detect a battery backup
module it refuses to go into writeback mode.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christian Schröder 2007-08-22 17:07:20 "out of memory" error
Previous Message Dmitry Koterov 2007-08-22 15:28:39 Postgres, fsync and RAID controller with 100M of internal cache & dedicated battery