Skip to contentSkip to conversation

Bad page state in process 'nfsd' with xfs

DISCUSSION David Greaves 4 participants 5 messages Apr 28, 2006 – May 1, 2006

lore
Share & tools
lore
#0 lore 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-----

#1 lore raw
Quoted 10 lines · David Greaves

-----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)

Quoted 8 lines

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.

Signature · 2 lines
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 
#2 lore raw
In reply to David Greaves

Hi there,

Quoted 9 lines · David Greaves

-----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)

Really old (early 2.6) or previously with 4Kstacks this used to be a problem, but should not be with your kernel version.

Quoted 8 lines

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

Hmm... so, your page flags field there (0x80000008) has the 33rd and 4th bits set - 4 is pageuptodate, which is fine, but 33 seems odd (perhaps some arch-specific bit? or a single bit error...).

But, the warning is triggered by the page count (16777216 above), and that is 0x1000000 -- which is a huge, improbable count; that looks to me like it could very well be the result of a single bit error too.

You may have a hardware problem - try running memtest I guess.

cheers.

Signature · 1 line
Nathan
#3 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 9 lines · Nathan Scott

Hi there,

On Fri, Apr 28, 2006 at 09:22:23PM +0100, David Greaves wrote:

But, the warning is triggered by the page count (16777216 above), and that is 0x1000000 -- which is a huge, improbable count; that looks to me like it could very well be the result of a single bit error too.

You may have a hardware problem - try running memtest I guess.

Thanks guys

It's in use a lot so I'll schedule some downtime, blow out the dust and run memtest (though I've done that before and it has been clean).

I'll let you know how it goes...

David

- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEVdfn8LvjTle4P1gRAiHTAKCBakrWQCpHgo8qyfN6ZNryAxi3bQCdFkDn vQe781l5bQvq1a5BG2nF5sk=
=jdAy
-----END PGP SIGNATURE-----

#4 lore raw
Quoted 3 lines · David Greaves

It's in use a lot so I'll schedule some downtime, blow out the dust and run memtest (though I've done that before and it has been clean).

memtest doesn't always find bad memory sadly

finding bad memory is hard, and sometimes it's exacerbated by complicated factors (heat from drives for example)

i wish ecc memory was standard