From: Lachlan McIlroy <lachlan@sgi.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] Re-dirty pages on I/O error
Date: Tue, 10 Feb 2009 12:48:38 +1100 [thread overview]
Message-ID: <4990DCF6.5000900@sgi.com> (raw)
[This patch seems to have slipped through the proverbial crack.]
If we get an error in xfs_page_state_convert() - and it's not EAGAIN - then
we throw away the dirty page without converting the delayed allocation. This
leaves delayed allocations that can never be removed and confuses code that
expects a flush of the file to clear them. We need to re-dirty the page on
error so we can try again later or report that the flush failed.
Index: xfs-fixes/fs/xfs/linux-2.6/xfs_aops.c
===================================================================
--- xfs-fixes.orig/fs/xfs/linux-2.6/xfs_aops.c
+++ xfs-fixes/fs/xfs/linux-2.6/xfs_aops.c
@@ -1185,16 +1185,6 @@ error:
if (iohead)
xfs_cancel_ioend(iohead);
- /*
- * If it's delalloc and we have nowhere to put it,
- * throw it away, unless the lower layers told
- * us to try again.
- */
- if (err != -EAGAIN) {
- if (!unmapped)
- block_invalidatepage(page, 0);
- ClearPageUptodate(page);
- }
return err;
}
@@ -1223,7 +1213,7 @@ xfs_vm_writepage(
struct page *page,
struct writeback_control *wbc)
{
- int error;
+ int error = 0;
int need_trans;
int delalloc, unmapped, unwritten;
struct inode *inode = page->mapping->host;
@@ -1269,19 +1259,16 @@ xfs_vm_writepage(
* to real space and flush out to disk.
*/
error = xfs_page_state_convert(inode, page, wbc, 1, unmapped);
- if (error == -EAGAIN)
- goto out_fail;
if (unlikely(error < 0))
- goto out_unlock;
+ goto out_fail;
return 0;
out_fail:
redirty_page_for_writepage(wbc, page);
unlock_page(page);
- return 0;
-out_unlock:
- unlock_page(page);
+ if (error == -EAGAIN)
+ error = 0;
return error;
}
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-02-10 1:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 1:48 Lachlan McIlroy [this message]
2009-02-10 10:01 ` [PATCH] Re-dirty pages on I/O error Dave Chinner
2009-02-10 23:33 ` Lachlan McIlroy
2009-02-15 20:05 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2008-09-11 8:37 Lachlan McIlroy
2008-09-11 10:33 ` Christoph Hellwig
2008-09-11 21:21 ` Eric Sandeen
2008-09-12 6:44 ` Lachlan McIlroy
2008-09-12 13:17 ` Eric Sandeen
2008-09-12 6:04 ` Lachlan McIlroy
2008-09-13 4:19 ` Dave Chinner
2008-09-15 3:22 ` Lachlan McIlroy
2008-09-16 4:01 ` Dave Chinner
2008-09-16 6:30 ` Lachlan McIlroy
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=4990DCF6.5000900@sgi.com \
--to=lachlan@sgi.com \
--cc=xfs@oss.sgi.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