|Subject:||3ware hardware raid with battery backup and the impact on barrier and no write cache options.|
|From:||William Lewis <william@xxxxxxxxxxxxxx>|
|Date:||Mon, 2 Nov 2009 20:02:20 +0000|
I am in the process of setting up an XFS file system on underlying hardware consisting of a 3ware 9550SXU (+ battery backup module) and 4 x Seagate ST31500341AS 1.5TB hard drives in Raid 5 configuration.
Reading your FAQ at http://xfs.org/index.php/XFS_FAQ I understand that it is advisable to mount the file system with nobarrier to improve performance. However going on to read about recommended settings for write cache, the advice for 3ware hardware doesn't seem to account for the fact that there are 2 levels of write cache in play, that in the 3ware card itself protected by the battery and the write cache of the disks themselves, which as far as I can understand is also protected by the battery backup (in the correct storage modes - balanced/protection) because the 3ware card uses write journaling to keep track of pending write operations in the disks' cache. Therefore unless I am misunderstanding something the most benefit is to be gained by mounting with nobarrier and having the write cache turned on?
One thing I am not clear about is if nobarrier interacts with the page cache at all and if the lack of barrier leaves you with a situation in which pending writes can be lost from main memory on power failure?
Thanks in advance for any clarification you can provide.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH] xfststests 220: test for prealloc/delalloc/reserved spacerecapture, Eric Sandeen|
|Next by Date:||RE: [PATCH] xfs: I/O completion handlers must use NOFS allocations, Alex Elder|
|Previous by Thread:||RE: [PATCH] xfststests 220: test for prealloc/delalloc/reserved spacerecapture, Alex Elder|
|Next by Thread:||Re: 3ware hardware raid with battery backup and the impact on barrier and no write cache options., Justin Piszcz|
|Indexes:||[Date] [Thread] [Top] [All Lists]|