Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Write\s+barriers\s+and\s+hardware\s+RAID\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Write\s+barriers\s+and\s+hardware\s+RAID\s*$/: 3 ]

Total 3 documents matching your query.

1. Write barriers and hardware RAID (score: 1): Author: J Pälve <xtc@xxxxxxx>; Date: Fri, 17 Jul 2009 13:35:52 +0300 (EEST); Hi, I'm setting up a server to provide storage for a couple of VMware ESXi servers. I'm using the latest stable Debian and I'm leaning towards using NFS with XFS. However, I'm concerned about data in; /archives/xfs/2009-07/msg00159.html (7,200 bytes)
2. Re: Write barriers and hardware RAID (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Mon, 20 Jul 2009 13:01:01 +0200; I wrote that sections of the FAQ, so I should answer: I guess it's only the "hard disk cache" turned on leading to better performance. But that is a very, very dangerous setup: If you use a RAID with; /archives/xfs/2009-07/msg00198.html (10,399 bytes)
3. Re: Write barriers and hardware RAID (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Tue, 21 Jul 2009 10:12:26 +0200; Please keep the discussion on the list also for others who search the same info later. If you use a RAID controller but then it allows cache flushes from the host to really flush it's cache, it's bas; /archives/xfs/2009-07/msg00212.html (10,217 bytes)

Current List: 1 - 3
Page: [1]