public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: David Greaves <david@dgreaves.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	linux-xfs@oss.sgi.com
Subject: Re: Bad page state in process 'nfsd' with xfs
Date: Sun, 30 Apr 2006 12:06:09 +1000	[thread overview]
Message-ID: <44541B91.3060104@yahoo.com.au> (raw)
In-Reply-To: <4452797F.70700@dgreaves.com>

David Greaves wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> This was with 2.6.16.9
> 
> There's an nfs export from an xfs on an lvm on a raid5 on some
> libata/sata disks.
> (cc'ing xfs since I recall rumoured(?) badness in old nfs/xfs/md/lvm
> setups and xfs_sendfile is mentioned)
> 
> dmesg had:
> 
> Bad page state in process 'nfsd'
> page:b1602060 flags:0x80000008 mapping:00000000 mapcount:0 count:16777216
> Trying to fix it up, but a reboot is needed
> Backtrace:
>  [<b013bda2>] bad_page+0x62/0x90
>  [<b013c1c8>] prep_new_page+0x78/0x80

Looks like you have a bit flipped in 'count', which was not flipped
when the page was last freed. Probably buggy RAM.

Running memtest overnight might confirm that.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-04-30  2:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 20:22 Bad page state in process 'nfsd' with xfs David Greaves
2006-04-30  2:06 ` Nick Piggin [this message]
2006-04-30 22:04 ` Nathan Scott
2006-05-01  9:41   ` David Greaves
2006-05-01 15:21     ` Chris Wedgwood
  -- strict thread matches above, loose matches on Subject: below --
2006-04-30 15:19 Zoltan Boszormenyi
2006-05-01  0:24 ` Nathan Scott
2006-05-01  8:07   ` Zoltan Boszormenyi
2006-05-01 21:33     ` Nathan Scott
2006-05-01 22:08       ` Zoltan Boszormenyi

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=44541B91.3060104@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=david@dgreaves.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-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