From: Christoph Hellwig <hch@infradead.org>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs-dev <xfs-dev@sgi.com>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] Prevent log tail pushing from blocking on buffer locks
Date: Thu, 24 Jul 2008 01:45:31 -0400 [thread overview]
Message-ID: <20080724054531.GA17215@infradead.org> (raw)
In-Reply-To: <48881788.7010709@sgi.com>
On Thu, Jul 24, 2008 at 03:47:52PM +1000, Lachlan McIlroy wrote:
>> The stuck propagation looks good, but I don't think this should be
>> blindly done for all errors. The only error where it makes sense is
>> the EAGAIN from xfs_iflush. All other returns inside the item_push
>> handlers basically indicate filesystem corruption.
>
> Good point. Regardless of the error it's still an item that could not
> be pushed and is effectively 'stuck'. What do you recommend I do for
> other errors? Shutdown the filesystem?
Good questions. When I did a quick audit many error do in fact come
from tests for shutdown filesystems, so they shouldn't ever happens.
So maybe add an assert that we're never getting here for shut down
filesystems and otherwise shut it down.
But all this is getting a little complicated and riksy, so I'd say push
your original patch in first and make the error handling a second one.
next prev parent reply other threads:[~2008-07-24 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 6:32 [PATCH] Prevent log tail pushing from blocking on buffer locks Lachlan McIlroy
2008-07-23 11:21 ` Christoph Hellwig
2008-07-24 5:47 ` Lachlan McIlroy
2008-07-24 5:45 ` Christoph Hellwig [this message]
2008-07-24 11:41 ` Dave Chinner
2008-07-25 1:32 ` 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=20080724054531.GA17215@infradead.org \
--to=hch@infradead.org \
--cc=lachlan@sgi.com \
--cc=xfs-dev@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