Topic: Badness in __writeback_single_inode

[Paperguides]

On checking the logs on a customers server I found the following in the message log:

Sep  3 01:40:58 thurley kernel: at fs/fs-writeback.c:248
Sep  3 01:40:58 thurley kernel:  [__writeback_single_inode+65/186] __writeback_single_inode+0x41/0xba
Sep  3 01:40:58 thurley kernel:  [<c017a011>] __writeback_single_inode+0x41/0xba
Sep  3 01:40:58 thurley kernel:  [write_inode_now_err+84/149] write_inode_now_err+0x54/0x95
Sep  3 01:40:58 thurley kernel:  [<f8ac2aba>] udf_clear_inode+0x6c/0x82 [udf]
Sep  3 01:40:58 thurley kernel:  [clear_inode+204/258] clear_inode+0xcc/0x102
Sep  3 01:40:58 thurley kernel:  [<c0173594>] clear_inode+0xcc/0x102
Sep  3 01:40:58 thurley kernel:  [dispose_list+71/109] dispose_list+0x47/0x6d
Sep  3 01:40:58 thurley kernel:  [<c0173611>] dispose_list+0x47/0x6d
Sep  3 01:40:58 thurley kernel:  [invalidate_inodes+160/185] invalidate_inodes+0xa0/0xb9
Sep  3 01:40:58 thurley kernel:  [<c0173854>] invalidate_inodes+0xa0/0xb9
Sep  3 01:40:58 thurley kernel:  [generic_shutdown_super+136/336] generic_shutdown_super+0x88/0x150
Sep  3 01:40:58 thurley kernel:  [<c01620b2>] generic_shutdown_super+0x88/0x150
Sep  3 01:40:58 thurley kernel:  [kill_block_super+12/27] kill_block_super+0xc/0x1b
Sep  3 01:40:58 thurley kernel:  [<c0162ab4>] kill_block_super+0xc/0x1b
Sep  3 01:40:58 thurley kernel:  [deactivate_super+91/112] deactivate_super+0x5b/0x70
Sep  3 01:40:58 thurley kernel:  [<c0161f78>] deactivate_super+0x5b/0x70
Sep  3 01:40:58 thurley kernel:  [sys_umount+101/108] sys_umount+0x65/0x6c
Sep  3 01:40:58 thurley kernel:  [<c0176432>] sys_umount+0x65/0x6c
Sep  3 01:40:58 thurley kernel:  [do_munmap+264/278] do_munmap+0x108/0x116
Sep  3 01:40:58 thurley kernel:  [<c015244a>] do_munmap+0x108/0x116
Sep  3 01:40:58 thurley kernel:  [do_page_fault+0/1478] do_page_fault+0x0/0x5c6
Sep  3 01:40:58 thurley kernel:  [<c011ae91>] do_page_fault+0x0/0x5c6
Sep  3 01:40:58 thurley kernel:  [error_code+47/56] error_code+0x2f/0x38
Sep  3 01:40:58 thurley kernel:  [<c02e1527>] error_code+0x2f/0x38
Sep  3 01:40:58 thurley kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Sep  3 01:40:58 thurley kernel:  [<c02e0a2f>] syscall_call+0x7/0xb

Can anyone tell me what it means?

The server appears to working fine and the daily backups are completing with out error.

There are two minor problems with the server I know about:

1) I am no longer receiving the summary email from DAR.  I have checked and reloaded the forwarding email address in the admin ID.

2) The software installer web page no longer indicates when updates are available.  I have used Yum update from the command line which get around the problem.

I have done searches of the Forums for solutions without success.

Tony

[jester]

Please search first! You'll find a similar report in the bug-tracker.

[Paperguides]

Sorry for that.  I did a Forum search but didn't look at the bugs list.

To save other people with the same problem doing the search; It is a known kernel bug relating to the use of a Iomega optical re-write drive.  I *think* the bug report at Red Hat indicates it may be fixed when the next release.

Another search turned up an answer to my second symptom.  If you have the same problem see Bug 4583.

I couldn't find anything on the first point (DAR not sending the summary email) so I'll start a bug report on that.

Tony