| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Scott Carey" <scott(at)richrelevance(dot)com> |
| Cc: | "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, Henrik <henke(at)mac(dot)se>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Filesystem benchmarking for pg 8.3.3 server |
| Date: | 2008-08-13 00:48:04 |
| Message-ID: | dcc563d10808121748o79a6f667tdec70c96a06b81f9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Aug 12, 2008 at 6:23 PM, Scott Carey <scott(at)richrelevance(dot)com> wrote:
> Some SATA drives were known to not flush their cache when told to.
> Some file systems don't know about this (UFS, older linux kernels, etc).
>
> So yes, if your OS / File System / Controller card combo properly sends the
> write cache flush command, and the drive is not a flawed one, all is well.
> Most should, not all do. Any one of those bits along the chain can
> potentially be disk write cache unsafe.
I can attest to the 2.4 kernel not being able to guarantee fsync on
IDE drives. And to the LSI megaraid SCSI controllers of the era
surviving numerous power off tests.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | david | 2008-08-13 01:33:08 | Re: Filesystem benchmarking for pg 8.3.3 server |
| Previous Message | Ron Mayer | 2008-08-13 00:40:18 | Re: Filesystem benchmarking for pg 8.3.3 server |