[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Jens Axboe <jaxboe fusionio com>
- To: Ric Wheeler <rwheeler redhat com>
- Cc: "tytso mit edu" <tytso mit edu>, "linux-scsi vger kernel org" <linux-scsi vger kernel org>, "linux-ide vger kernel org" <linux-ide vger kernel org>, "jack suse cz" <jack suse cz>, "linux-kernel vger kernel org" <linux-kernel vger kernel org>, "swhiteho redhat com" <swhiteho redhat com>, "linux-raid vger kernel org" <linux-raid vger kernel org>, "linux-fsdevel vger kernel org" <linux-fsdevel vger kernel org>, "dm-devel redhat com" <dm-devel redhat com>, "James Bottomley suse de" <James Bottomley suse de>, "konishi ryusuke lab ntt co jp" <konishi ryusuke lab ntt co jp>, Tejun Heo <tj kernel org>, "vst vlnb net" <vst vlnb net>, Christoph Hellwig <hch lst de>, "chris mason oracle com" <chris mason oracle com>
- Subject: Re: [dm-devel] [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- Date: Mon, 23 Aug 2010 16:01:15 +0200
On 2010-08-23 15:58, Ric Wheeler wrote:
> On 08/23/2010 08:48 AM, Christoph Hellwig wrote:
>> On Mon, Aug 23, 2010 at 02:30:33PM +0200, Tejun Heo wrote:
>>> It might be useful to give several example configurations with
>>> different cache configurations. I don't have much experience with
>>> battery backed arrays but aren't they suppose to report write through
>>> cache automatically?
>>
>> They usually do. I have one that doesn't, but SYNCHRONIZE CACHE on
>> it is so fast that it effectively must be a no-op.
>>
>
> Arrays are not a problem in general - they normally have internally, redundant
> batteries to hold up the cache.
>
> The issue is when you have an internal hardware RAID card with a large cache.
> Those cards sit in your server and the batteries on the card protect its
> internal cache, but do not have the capacity to hold up the drives behind it.
>
> Normally, those drives should have their write cache disabled, but sometimes
> (especially with S-ATA disks) this is not done.
The problem purely exists on arrays that report write back cache enabled
AND don't implement SYNC_CACHE as a noop. Do any of them exist, or are
they purely urban legend?
--
Jens Axboe
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]