From: Dave Chinner <david@fromorbit.com>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] make inode reclaim wait for log I/O to complete
Date: Wed, 18 Jun 2008 14:30:02 +1000 [thread overview]
Message-ID: <20080618043002.GS3700@disturbed> (raw)
In-Reply-To: <48588E6B.3010006@sgi.com>
On Wed, Jun 18, 2008 at 02:26:19PM +1000, Lachlan McIlroy wrote:
> ping.
>
> Lachlan McIlroy wrote:
>> During a forced shutdown a xfs inode can be destroyed before log
>> I/O involving that inode is complete. We need to wait for the
>> inode to be unpinned before tearing it down. Version 2 cleans up
>> the code a bit by relying on xfs_iflush() to do the unpinning and
>> forced shutdown check.
Sorry I missed this when you first posted it. This one looks ok.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-06-18 4:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 4:55 [PATCH V2] make inode reclaim wait for log I/O to complete Lachlan McIlroy
2008-06-18 4:26 ` Lachlan McIlroy
2008-06-18 4:30 ` Dave Chinner [this message]
2008-06-18 6:40 ` 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=20080618043002.GS3700@disturbed \
--to=david@fromorbit.com \
--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