From: David Greaves <david@dgreaves.com>
To: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
linux-xfs@oss.sgi.com
Subject: Bad page state in process 'nfsd' with xfs
Date: Fri, 28 Apr 2006 21:22:23 +0100 [thread overview]
Message-ID: <4452797F.70700@dgreaves.com> (raw)
-----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
[<b013c6b6>] buffered_rmqueue+0xf6/0x1f0
[<b013c8e2>] get_page_from_freelist+0x92/0xb0
[<b013c956>] __alloc_pages+0x56/0x300
[<b013f00c>] __do_page_cache_readahead+0xdc/0x120
[<b013f1b9>] blockable_page_cache_readahead+0x59/0xd0
[<b013f2aa>] make_ahead_window+0x7a/0xb0
[<b013f39f>] page_cache_readahead+0xbf/0x1b0
[<b0138b91>] do_generic_mapping_read+0x4b1/0x4c0
[<b01390e2>] generic_file_sendfile+0x62/0x70
[<f1097080>] nfsd_read_actor+0x0/0xd0 [nfsd]
[<b021bab0>] xfs_sendfile+0xc0/0x190
[<f1097080>] nfsd_read_actor+0x0/0xd0 [nfsd]
[<b0217fe8>] linvfs_open+0x48/0x50
[<b0217f97>] linvfs_sendfile+0x57/0x60
[<f1097080>] nfsd_read_actor+0x0/0xd0 [nfsd]
[<f109734f>] nfsd_vfs_read+0x1ff/0x370 [nfsd]
[<f1097080>] nfsd_read_actor+0x0/0xd0 [nfsd]
[<f1097933>] nfsd_read+0x103/0x120 [nfsd]
[<f109e234>] nfsd3_proc_read+0xe4/0x170 [nfsd]
[<f1093649>] nfsd_dispatch+0xd9/0x210 [nfsd]
[<f10e4792>] svc_process+0x482/0x670 [sunrpc]
[<f10933fc>] nfsd+0x18c/0x300 [nfsd]
[<f1093270>] nfsd+0x0/0x300 [nfsd]
[<b0101391>] kernel_thread_helper+0x5/0x14
more info on request but I have rebooted as suggested.
David
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEUnl+8LvjTle4P1gRAip3AJ9izpp3+/6/fPgzSbJdxuc74Uus5wCZAWtF
QHY+xcDh9cf6bYhBCx+DzJE=
=XZDc
-----END PGP SIGNATURE-----
next reply other threads:[~2006-04-28 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 20:22 David Greaves [this message]
2006-04-30 2:06 ` Bad page state in process 'nfsd' with xfs Nick Piggin
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=4452797F.70700@dgreaves.com \
--to=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 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.