From: "Steve French (smfltc)" <smfltc@us.ibm.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Shirish S Pargaonkar <shirishp@us.ibm.com>,
shaggy@linux.vnet.ibm.com, linux-fsdevel@vger.kernel.org
Subject: flush and EIO errors when writepages fails
Date: Fri, 20 Jun 2008 11:19:19 -0500 [thread overview]
Message-ID: <485BD887.8090608@us.ibm.com> (raw)
In-Reply-To: <20080620091542.09edb43f@tupile.poochiereds.net>
If flush fails to write all dirty pages (due to an I/O error on the
server, server disk or networking stack) today the error (EIO) is marked
in the inode, and returned on close. I think cifs_flush (which is
called before close by the vfs) should also (perhaps after sleep a
second or so then) retry at least once on the filemap_fdatawrite before
giving up. (perhaps retry more if mounted hard) Thoughts?
next parent reply other threads:[~2008-06-20 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080620073150.2bc9988e@tupile.poochiereds.net>
[not found] ` <OFE8C66E61.981E25D1-ON8725746E.0045A92A-8625746E.004718C0@us.ibm.com>
[not found] ` <20080620091542.09edb43f@tupile.poochiereds.net>
2008-06-20 16:19 ` Steve French (smfltc) [this message]
2008-06-20 16:34 ` flush and EIO errors when writepages fails Jeff Layton
2008-06-20 16:41 ` Steve French (smfltc)
2008-06-20 17:12 ` Jeff Layton
2008-06-20 22:34 Steve French
2008-06-21 7:05 ` Evgeniy Polyakov
2008-06-21 12:27 ` Jeff Layton
2008-06-21 13:19 ` Evgeniy Polyakov
2008-06-21 14:21 ` Jody French
2008-06-21 14:42 ` Evgeniy Polyakov
2008-06-21 16:15 ` Steve French
2008-06-21 16:28 ` Evgeniy Polyakov
2008-06-21 17:02 ` Steve French
2008-06-21 17:26 ` Evgeniy Polyakov
2008-06-21 17:37 ` Evgeniy Polyakov
2008-06-23 15:39 ` Dave Kleikamp
2008-06-23 18:05 ` Dave Kleikamp
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=485BD887.8090608@us.ibm.com \
--to=smfltc@us.ibm.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=shirishp@us.ibm.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;
as well as URLs for NNTP newsgroup(s).