CEPH filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: idryomov@gmail.com, zyan@redhat.com, sage@redhat.com
Cc: jspray@redhat.com, ceph-devel@vger.kernel.org
Subject: [PATCH v7 6/7] Revert "ceph: SetPageError() for writeback pages if writepages fails"
Date: Wed,  5 Apr 2017 13:14:16 -0400	[thread overview]
Message-ID: <20170405171417.25187-7-jlayton@redhat.com> (raw)
In-Reply-To: <20170405171417.25187-1-jlayton@redhat.com>

This reverts commit b109eec6f4332bd517e2f41e207037c4b9065094.

If I'm filling up a filesystem with this sort of command:

    $ dd if=/dev/urandom of=/mnt/cephfs/fillfile bs=2M oflag=sync

...then I'll eventually get back EIO on a write. Further calls
will give us ENOSPC.

I'm not sure what prompted this change, but I don't think it's what we
want to do. If writepages failed, we will have already set the mapping
error appropriately, and that's what gets reported by fsync() or
close().

__filemap_fdatawait_range however, does this:

	wait_on_page_writeback(page);
	if (TestClearPageError(page))
		ret = -EIO;

...and that -EIO ends up trumping the mapping's error if one exists.

When writepages fails, we only want to set the error in the mapping,
and not flag the individual pages.

Reviewed-by: "Yan, Zheng” <zyan@redhat.com>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
---
 fs/ceph/addr.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
index 7e3fae334620..6cdf94459ac4 100644
--- a/fs/ceph/addr.c
+++ b/fs/ceph/addr.c
@@ -703,9 +703,6 @@ static void writepages_finish(struct ceph_osd_request *req)
 				clear_bdi_congested(&fsc->backing_dev_info,
 						    BLK_RW_ASYNC);
 
-			if (rc < 0)
-				SetPageError(page);
-
 			ceph_put_snap_context(page_snap_context(page));
 			page->private = 0;
 			ClearPagePrivate(page);
-- 
2.9.3


  parent reply	other threads:[~2017-04-05 17:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 17:14 [PATCH v7 0/7] ceph: implement -ENOSPC handling in cephfs Jeff Layton
2017-04-05 17:14 ` [PATCH v7 1/7] libceph: remove req->r_replay_version Jeff Layton
2017-04-05 17:14 ` [PATCH v7 2/7] libceph: allow requests to return immediately on full conditions if caller wishes Jeff Layton
2017-04-05 17:14 ` [PATCH v7 3/7] libceph: abort already submitted but abortable requests when map or pool goes full Jeff Layton
2017-04-05 17:14 ` [PATCH v7 4/7] libceph: add an epoch_barrier field to struct ceph_osd_client Jeff Layton
2017-04-10 10:45   ` Jeff Layton
2017-04-05 17:14 ` [PATCH v7 5/7] ceph: handle epoch barriers in cap messages Jeff Layton
2017-04-05 17:14 ` Jeff Layton [this message]
2017-04-05 17:14 ` [PATCH v7 7/7] ceph: when seeing write errors on an inode, switch to sync writes Jeff Layton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170405171417.25187-7-jlayton@redhat.com \
    --to=jlayton@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=jspray@redhat.com \
    --cc=sage@redhat.com \
    --cc=zyan@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox