xfs
[Top] [All Lists]

Re: XFS and DPX files

To: xfs@xxxxxxxxxxx
Subject: Re: XFS and DPX files
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 3 Nov 2009 21:58:29 +0100
In-reply-to: <20091103121920.7e6b6d07@xxxxxxxxxxxxxxxxxxxx>
Organization: it-management http://it-management.at
References: <4AEC2CF4.8040703@xxxxxxx> <200911022258.35164@xxxxxx> <20091103121920.7e6b6d07@xxxxxxxxxxxxxxxxxxxx>
User-agent: KMail/1.10.3 (Linux/2.6.31.4-ZMI; KDE/4.1.3; x86_64; ; )
On Dienstag 03 November 2009 Emmanuel Florac wrote:
> Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx> écrivait:
> > Hence my suggestion for turning on the disk write cache just to see
> > if it makes a difference.
>
> Unfortunately there isn't any way in the 3Ware controllers to manage
> that. Worse, I couldn't get a clear answer from 3Ware support about
> the controller policy about drives caches. However from the tests
> I've done (pulling the plug on a server while writing) it looks like
> the 3Ware uses the disks caches in write-thru mode, however
> (fortunately now that many drives come with 32 or 64 MB caches).
>
> Some other SATA/SAS RAID controllers (Areca, LSI and Adaptec) allows
> to activate drive write-back cache separately from the controller
> cache, though.

Looks like you didn't read the FAQ until now, I tried to document the 
unclear bits as good as I could:

http://www.xfs.org/index.php/XFS_FAQ#Q._Which_settings_does_my_RAID_controller_need_.3F

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4

<Prev in Thread] Current Thread [Next in Thread>