From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/3] xfs: truncate delalloc extents when IO fails in writeback
Date: Wed, 10 Mar 2010 04:12:37 -0500 [thread overview]
Message-ID: <20100310091237.GA25227@infradead.org> (raw)
In-Reply-To: <1267667185-7736-3-git-send-email-david@fromorbit.com>
Btw, I can trigger the new warnings from this patch in xfsqa after
a few full XFSQA runs:
[39829.737139] Filesystem "vdb6": page discard on page c21d7480, inode
0x3f8, offset 0.
[39829.739488] Filesystem "vdb6": page discard failed delalloc mapping
lookup.
[39829.744005] Filesystem "vdb6": page discard on page c206ba80, inode
0x3f9, offset 0.
[39829.746496] Filesystem "vdb6": page discard failed delalloc mapping
lookup.
[39829.748655] Filesystem "vdb6": page discard on page c20e02a0, inode
0x3fa, offset 0.
[39829.751000] Filesystem "vdb6": page discard failed delalloc mapping
lookup.
going on for a few pages of kernel messages.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-03-10 9:11 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 ` Christoph Hellwig [this message]
2010-03-10 12:52 ` [PATCH 2/3] " Dave Chinner
2010-03-10 18:18 ` Christoph Hellwig
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=20100310091237.GA25227@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox