Skip to contentSkip to conversation

Bad page state in process 'nfsd' with xfs

DISCUSSION Zoltan Boszormenyi 2 participants 5 messages Apr 30, 2006 – May 1, 2006

lore
Share & tools
lore
#0 lore raw

Hi.

Quoted 20 lines
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
Quoted 4 lines

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.

Or not. I had an FC3/x86-64 system until two days ago, now I have FC5/86-64.

When FC3 was installed I chose to format the partitions to XFS and since then I had Oopses regularly with or without VMWare modules.
I have run memtest64+ for 12+ hours and it indicated two separate single bit errors in the topmost 64MB of my 1GB. Since then I was running with mem=960M but I still got Oopses on a bit heavier disk loads and every time XFS was involved.

I backed up my /home with rsync to a new harddisk in single mode, the new disk was formatted to EXT3. During the backup I had Oopses about 5 or 6 times and I had to reboot. Rsync was able to continue, that's why I chose that for backup...

I installed FC5 using only EXT3 partitions and copied my 80+ GB data back to /home. Guess what? No Oopses...

Best regards,
Zoltán Böszörményi

#1 lore raw
Quoted 6 lines · Zoltan Boszormenyi

...
Or not. I had an FC3/x86-64 system until two days ago, now I have FC5/86-64.

When FC3 was installed I chose to format the partitions to XFS and since then
I had Oopses regularly with or without VMWare modules.

What was the stack trace for your oops...?

cheers.

Signature · 1 line
Nathan
#2 lore raw

Hi,

Nathan Scott írta:

Quoted 5 lines · Zoltan Boszormenyi
Quoted 4 lines

...
Or not. I had an FC3/x86-64 system until two days ago, now I have FC5/86-64.

Quoted 8 lines
Quoted 3 lines

When FC3 was installed I chose to format the partitions to XFS and since then I had Oopses regularly with or without VMWare modules.

What was the stack trace for your oops...?

cheers.

I reported some Oopses for earlier kernels, they are here:

http://marc.theaimsgroup.com/?t=113649735300003&r=1&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=113166035904096&w=2
http://marc.theaimsgroup.com/?l=fedora-list&m=113611408900505&w=2

With FC3, the last kernel I used was vanilla 2.6.15. It may be that those above were fixed since.

Best regards,
Zoltán Böszörményi

#3 lore raw
Quoted 13 lines · Zoltan Boszormenyi

Hi,

Nathan Scott írta:

Quoted 10 lines · Zoltan Boszormenyi
Quoted 8 lines

...
Or not. I had an FC3/x86-64 system until two days ago, now I have FC5/86-64.

When FC3 was installed I chose to format the partitions to XFS and since then
I had Oopses regularly with or without VMWare modules.

Quoted 6 lines
Quoted 4 lines

What was the stack trace for your oops...?

cheers.

I reported some Oopses for earlier kernels, they are here:

These aren't oopses. They do look similar, but slightly different to the other report - your page count there is off with the pixies, but its not as clear that its a single bit error - yours are more like 0xfffe0000. Quite strange. You also have the odd high-32-bits-mirrors-low-32-bits in page flags, both with one bit set.

Not sure XFS can be causing this (we don't touch page count for regular file pages, and only touch PageUptodate in flags IIRC, like most/all filesystems).

Were you also using NFS, as in the other report?

cheers.

Signature · 1 line
Nathan
#4 lore raw

Hi,

Nathan Scott írta:

Quoted 31 lines · Zoltan Boszormenyi
Quoted 15 lines

Hi,

Nathan Scott írta:

Quoted 10 lines · Zoltan Boszormenyi
Quoted 9 lines

...
Or not. I had an FC3/x86-64 system until two days ago, now I have FC5/86-64.

When FC3 was installed I chose to format the partitions to XFS and since then I had Oopses regularly with or without VMWare modules.

Quoted 7 lines
Quoted 5 lines

What was the stack trace for your oops...?

cheers.

I reported some Oopses for earlier kernels, they are here:

These aren't oopses. They do look similar, but slightly different to the other report - your page count there is off with the pixies, but its not as clear that its a single bit error - yours are more like 0xfffe0000. Quite strange. You also have the odd high-32-bits-mirrors-low-32-bits in page flags, both with one bit set.

Quoted 9 lines

Not sure XFS can be causing this (we don't touch page count for regular file pages, and only touch PageUptodate in flags IIRC, like most/all filesystems).

Were you also using NFS, as in the other report?

cheers.

No, it's just a standalone machine.

Best regards,
Zoltán Böszörményi