[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: Alan Cox <alan lxorguk ukuu org uk>
- To: Vladislav Bolkhovitin <vst vlnb net>
- Cc: Kiyoshi Ueda <k-ueda ct jp nec com>, tytso mit edu, linux-scsi vger kernel org, linux-ide vger kernel org, jaxboe fusionio com, linux-kernel vger kernel org, swhiteho redhat com, linux-raid vger kernel org, linux-fsdevel vger kernel org, dm-devel redhat com, James Bottomley suse de, konishi ryusuke lab ntt co jp, Tejun Heo <tj kernel org>, jack suse cz, rwheeler redhat com, Christoph Hellwig <hch lst de>, chris mason oracle com
- Subject: Re: [dm-devel] [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- Date: Wed, 25 Aug 2010 00:14:21 +0100
> In SCSI there are conditions when a command, including FLUSH
> (SYNC_CACHE), failed which don't imply lost data. For them the caller
> expected to retry the failed command. Most common cases are Unit
> Attentions and TASK QUEUE FULL status.
ATA expects the command to be retried as well because a failed flush
indicates the specific sector is lost (unless the host still has a copy
of course - which is *very* likely although we don't use it) but the rest
of the flush transaction can be retried to continue to flush sectors
beyond the failed one.
Alan
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]