From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CFF92C433E0 for ; Tue, 23 Jun 2020 16:49:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AC0BA204EA for ; Tue, 23 Jun 2020 16:49:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Mh6FC/3d" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732548AbgFWQtl (ORCPT ); Tue, 23 Jun 2020 12:49:41 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:25928 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1732510AbgFWQtk (ORCPT ); Tue, 23 Jun 2020 12:49:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592930979; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=qv/pR3FyfWJFtIOvxO57ePJlwgy3dTWEly61Szbn7Ew=; b=Mh6FC/3dp+3RCvkBP8XHOSR6Hse9TpE0PDqehryKmOIiN2t8rQfZo+e24KBpOtc23UaVYX z1lBwN3bCStwBdqCC9+x15enOBBGuqqdrgGXCFHb7l5KJx7hPjaEVp6Drj6emQaPL5koqk cWaueZa68Pi9QuGJIerMGnWV3WFmwys= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-427-KoRAO1feNIK1Up3wvmciCg-1; Tue, 23 Jun 2020 12:49:37 -0400 X-MC-Unique: KoRAO1feNIK1Up3wvmciCg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 75179835B8D; Tue, 23 Jun 2020 16:49:36 +0000 (UTC) Received: from bfoster (dhcp-41-2.bos.redhat.com [10.18.41.2]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1D8675C290; Tue, 23 Jun 2020 16:49:36 +0000 (UTC) Date: Tue, 23 Jun 2020 12:49:34 -0400 From: Brian Foster To: "Darrick J. Wong" Cc: xfs , Dave Chinner Subject: Re: [PATCH v2] xfs: don't eat an EIO/ENOSPC writeback error when scrubbing data fork Message-ID: <20200623164934.GA56510@bfoster> References: <20200623035010.GF7606@magnolia> <20200623121031.GB55038@bfoster> <20200623152350.GE7625@magnolia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200623152350.GE7625@magnolia> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Sender: linux-xfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org On Tue, Jun 23, 2020 at 08:23:50AM -0700, Darrick J. Wong wrote: > On Tue, Jun 23, 2020 at 08:10:31AM -0400, Brian Foster wrote: > > On Mon, Jun 22, 2020 at 08:50:10PM -0700, Darrick J. Wong wrote: > > > From: Darrick J. Wong > > > > > > The data fork scrubber calls filemap_write_and_wait to flush dirty pages > > > and delalloc reservations out to disk prior to checking the data fork's > > > extent mappings. Unfortunately, this means that scrub can consume the > > > EIO/ENOSPC errors that would otherwise have stayed around in the address > > > space until (we hope) the writer application calls fsync to persist data > > > and collect errors. The end result is that programs that wrote to a > > > file might never see the error code and proceed as if nothing were > > > wrong. > > > > > > xfs_scrub is not in a position to notify file writers about the > > > writeback failure, and it's only here to check metadata, not file > > > contents. Therefore, if writeback fails, we should stuff the error code > > > back into the address space so that an fsync by the writer application > > > can pick that up. > > > > > > Fixes: 99d9d8d05da2 ("xfs: scrub inode block mappings") > > > Signed-off-by: Darrick J. Wong > > > --- > > > v2: explain why it's ok to keep going even if writeback fails > > > --- > > > fs/xfs/scrub/bmap.c | 19 ++++++++++++++++++- > > > 1 file changed, 18 insertions(+), 1 deletion(-) > > > > > > diff --git a/fs/xfs/scrub/bmap.c b/fs/xfs/scrub/bmap.c > > > index 7badd6dfe544..0d7062b7068b 100644 > > > --- a/fs/xfs/scrub/bmap.c > > > +++ b/fs/xfs/scrub/bmap.c > > > @@ -47,7 +47,24 @@ xchk_setup_inode_bmap( > > > sc->sm->sm_type == XFS_SCRUB_TYPE_BMBTD) { > > > inode_dio_wait(VFS_I(sc->ip)); > > > error = filemap_write_and_wait(VFS_I(sc->ip)->i_mapping); > > > - if (error) > > > + if (error == -ENOSPC || error == -EIO) { > > > + /* > > > + * If writeback hits EIO or ENOSPC, reflect it back > > > + * into the address space mapping so that a writer > > > + * program calling fsync to look for errors will still > > > + * capture the error. > > > + * > > > + * However, we continue into the extent mapping checks > > > + * because write failures do not necessarily imply > > > + * anything about the correctness of the file metadata. > > > + * The metadata and the file data could be on > > > + * completely separate devices; a media failure might > > > + * only affect a subset of the disk, etc. We properly > > > + * account for delalloc extents, so leaving them in > > > + * memory is fine. > > > + */ > > > + mapping_set_error(VFS_I(sc->ip)->i_mapping, error); > > > > I think the more appropriate thing to do is open code the data write and > > wait and use the variants of the latter that don't consume address space > > errors in the first place (i.e. filemap_fdatawait_keep_errors()). Then > > we wouldn't need the special error handling branch or perhaps the first > > part of the comment. Hm? > > Yes, it's certainly possible. I don't want to go opencoding more vfs > methods (like some e4 filesystems do) so I'll propose that as a second > patch for 5.9. > What's the point of fixing it twice when the generic code already exports the appropriate helpers? filemap_fdatawrite() and filemap_fdatawait_keep_errors() are used fairly commonly afaict. That seems much more straightforward to me than misusing a convenience helper and trying to undo the undesirable effects after the fact. > On second thought, I wonder if I should just drop the flush entirely? > It's not a huge burden to skip past the delalloc reservations. > > Hmmm. Any preferences? > The context for the above is not clear to me. If the purpose is to check on-disk metadata, shouldn't we flush the in-core content first? It would seem a little strange to me for one file check to behave differently from another if the only difference between the two is that some or more of a file had been written back, but maybe I'm missing details.. Brian > --D > > > Brian > > > > > + } else if (error) > > > goto out; > > > } > > > > > > > > >