All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 2/3] xfs: truncate delalloc extents when IO fails in writeback
Date: Wed, 10 Mar 2010 13:18:05 -0500	[thread overview]
Message-ID: <20100310181805.GA30829@infradead.org> (raw)
In-Reply-To: <20100310125219.GA16344@discord.disaster>

On Wed, Mar 10, 2010 at 11:52:19PM +1100, Dave Chinner wrote:
> The "page discard on page ...." are expected, but the failed mapping
> warnings are not - that means xfs_bmapi() returned an error while
> the inode still has delayed allocation buffers in memory. Did this
> happen during a forced shutdown?  What test is running when this
> occurs?

This is in test 137 which shuts down the filesystem.  I guess the
warning is indeed due to a shutdown filesystem and we should probably
not bother to warn for that case.  I'll give the obvious patch a try.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-03-10 18:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  1:46 [PATCH 0/3] xfs: delayed allocation @ ENOSPC fixes Dave Chinner
2010-03-04  1:46 ` [PATCH 1/3] xfs: check for more work before sleeping in xfssyncd Dave Chinner
2010-03-04 13:50   ` Christoph Hellwig
2010-03-04 22:56     ` Dave Chinner
2010-03-04  1:46 ` [PATCH 2/3] xfs: truncate delalloc extents when IO fails in writeback Dave Chinner
2010-03-04 14:28   ` Christoph Hellwig
2010-03-04 22:03     ` Dave Chinner
2010-03-05  2:00       ` [PATCH v2] " Dave Chinner
2010-03-05  9:21         ` Christoph Hellwig
2010-03-10  9:12   ` [PATCH 2/3] " Christoph Hellwig
2010-03-10 12:52     ` Dave Chinner
2010-03-10 18:18       ` Christoph Hellwig [this message]
2010-03-04  1:46 ` [PATCH 3/3] xfs: Increase the default size of the reserved blocks pool Dave Chinner
2010-03-05 15:45   ` Alex Elder
2010-03-05 23:26     ` Dave Chinner

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=20100310181805.GA30829@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.