Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754265Ab0FAQsT (ORCPT ); Tue, 1 Jun 2010 12:48:19 -0400 Received: from rcsinet10.oracle.com ([148.87.113.121]:60505 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753795Ab0FAQsR (ORCPT ); Tue, 1 Jun 2010 12:48:17 -0400 Date: Tue, 1 Jun 2010 12:47:50 -0400 From: Chris Mason To: Matthew Wilcox Cc: James Bottomley , Christof Schmitt , Boaz Harrosh , "Martin K. Petersen" , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: Wrong DIF guard tag on ext2 write Message-ID: <20100601164750.GQ8980@think> Mail-Followup-To: Chris Mason , Matthew Wilcox , James Bottomley , Christof Schmitt , Boaz Harrosh , "Martin K. Petersen" , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org References: <20100531112817.GA16260@schmichrtp.mainz.de.ibm.com> <1275318102.2823.47.camel@mulgrave.site> <4C03D5FD.3000202@panasas.com> <20100601103041.GA15922@schmichrtp.mainz.de.ibm.com> <1275398876.21962.6.camel@mulgrave.site> <20100601133341.GK8980@think> <1275399637.21962.11.camel@mulgrave.site> <20100601134951.GM8980@think> <20100601162929.GC32708@parisc-linux.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100601162929.GC32708@parisc-linux.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Auth-Type: Internal IP X-Source-IP: acsinet15.oracle.com [141.146.126.227] X-CT-RefId: str=0001.0A090204.4C0539C3.00AF:SCFMA922111,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1005 Lines: 24 On Tue, Jun 01, 2010 at 10:29:30AM -0600, Matthew Wilcox wrote: > On Tue, Jun 01, 2010 at 09:49:51AM -0400, Chris Mason wrote: > > > I agree that a block based retry would close all the holes ... it just > > > doesn't look elegant to me that the fs will already be repeating the I/O > > > if it changed the page and so will block. > > > > We might not ever repeat the IO. We might change the page, write it, > > change it again, truncate the file and toss the page completely. > > Why does it matter that it was never written in that case? It matters is the storage layer is going to wait around for the block to be written again with a correct crc. Unless there is trim + DIF, but that's a lot of plates to spin just for a basic implementation. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/