Debian remounted on following error... =/
Brought to you by:
blaschke-oss,
shaggyk
Menu
▾
▴
#244 Debian remounted on following error... =/
Badness in metapage_releasepage at
fs/jfs/jfs_metapage.c:564
[<c01bce61>] metapage_releasepage+0xd1/0x100
[<c015a491>] try_to_release_page+0x51/0x80
[<c01428c1>] pagevec_strip+0x51/0x60
[<c0144010>] refill_inactive_zone+0x210/0x460
[<c013e443>] get_writeback_state+0x43/0x50
[<c013e46c>] get_dirty_limits+0x1c/0xe0
[<c013e766>] throttle_vm_writeout+0x36/0x80
[<c01432c8>] shrink_slab+0x88/0x190
[<c01442f1>] shrink_zone+0x91/0xe0
[<c014485c>] balance_pgdat+0x2dc/0x3d0
[<c0144a39>] kswapd+0xe9/0x110
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0103062>] ret_from_fork+0x6/0x14
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0144950>] kswapd+0x0/0x110
[<c010133d>] kernel_thread_helper+0x5/0x18
I was just surfing and noticed that firefox crashed, i
tried to start it again and it said my filesystem was
readonly, in dmesg the aforementioned was stated. I
rebooted and did a fsck which removed some files and
then everything was fine again. *breathes a sigh of
relief* no problems with my drive otherwise =/
Logged In: NO
It just happened again! the crap...
Badness in metapage_releasepage at fs/jfs/jfs_metapage.c:564
[<c01bce61>] metapage_releasepage+0xd1/0x100
[<c015a491>] try_to_release_page+0x51/0x80
[<c01428c1>] pagevec_strip+0x51/0x60
[<c014418c>] refill_inactive_zone+0x38c/0x460
[<c01442f1>] shrink_zone+0x91/0xe0
[<c014485c>] balance_pgdat+0x2dc/0x3d0
[<c0144a39>] kswapd+0xe9/0x110
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0103062>] ret_from_fork+0x6/0x14
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0144950>] kswapd+0x0/0x110
[<c010133d>] kernel_thread_helper+0x5/0x18
[<c01bce77>] metapage_releasepage+0xe7/0x100
[<c015a491>] try_to_release_page+0x51/0x80
[<c01428c1>] pagevec_strip+0x51/0x60
[<c0144010>] refill_inactive_zone+0x210/0x460
[<c013e443>] get_writeback_state+0x43/0x50
[<c013e46c>] get_dirty_limits+0x1c/0xe0
[<c013e766>] throttle_vm_writeout+0x36/0x80
[<c01432c8>] shrink_slab+0x88/0x190
[<c01442f1>] shrink_zone+0x91/0xe0
[<c014485c>] balance_pgdat+0x2dc/0x3d0
[<c0144a39>] kswapd+0xe9/0x110
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0103062>] ret_from_fork+0x6/0x14
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0144950>] kswapd+0x0/0x110
[<c010133d>] kernel_thread_helper+0x5/0x18
[<c01bce77>] metapage_releasepage+0xe7/0x100
[<c015a491>] try_to_release_page+0x51/0x80
[<c01428c1>] pagevec_strip+0x51/0x60
[<c0144010>] refill_inactive_zone+0x210/0x460
[<c01432c8>] shrink_slab+0x88/0x190
[<c01442f1>] shrink_zone+0x91/0xe0
[<c014485c>] balance_pgdat+0x2dc/0x3d0
[<c0144a39>] kswapd+0xe9/0x110
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0103062>] ret_from_fork+0x6/0x14
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0144950>] kswapd+0x0/0x110
[<c010133d>] kernel_thread_helper+0x5/0x18
[<c01bce77>] metapage_releasepage+0xe7/0x100
[<c015a491>] try_to_release_page+0x51/0x80
[<c01428c1>] pagevec_strip+0x51/0x60
[<c0144010>] refill_inactive_zone+0x210/0x460
[<c01432c8>] shrink_slab+0x88/0x190
[<c01442f1>] shrink_zone+0x91/0xe0
[<c014485c>] balance_pgdat+0x2dc/0x3d0
[<c0144a39>] kswapd+0xe9/0x110
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0103062>] ret_from_fork+0x6/0x14
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0144950>] kswapd+0x0/0x110
[<c010133d>] kernel_thread_helper+0x5/0x18
[<c01bce77>] metapage_releasepage+0xe7/0x100
[<c015a491>] try_to_release_page+0x51/0x80
[<c01428c1>] pagevec_strip+0x51/0x60
[<c0144010>] refill_inactive_zone+0x210/0x460
[<c013e443>] get_writeback_state+0x43/0x50
[<c013e46c>] get_dirty_limits+0x1c/0xe0
[<c013e766>] throttle_vm_writeout+0x36/0x80
[<c01432c8>] shrink_slab+0x88/0x190
[<c01442f1>] shrink_zone+0x91/0xe0
[<c014485c>] balance_pgdat+0x2dc/0x3d0
[<c0144a39>] kswapd+0xe9/0x110
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0103062>] ret_from_fork+0x6/0x14
[<c012bd80>] autoremove_wake_function+0x0/0x60
[<c0144950>] kswapd+0x0/0x110
[<c010133d>] kernel_thread_helper+0x5/0x18
and it keeps going and going with similar messages :'(((((
Logged In: YES
user_id=422440
The reported Badness is a warning that turned out to be
bogus, and has been removed as of the 2.6.13 kernel. It
should not have led to the crash or the file system being
mounted read-only. Did you save any later output from dmesg?
If you build your own kernel, you can just comment out the
WARN_ON statement at line 564 of jfs_metapage.c. I'm not
very up on debian. Is there a newer kernel you can install?
Logged In: YES
user_id=422440
Closing as fixed, since the reported stack trace was fixed
in 2.6.13, and I have no further detail on the rest of the
problem.