dbbackup messages in /var/log/messages

[BDMcGrew]

Good morning all,

I'm running TSM 7.1 on CentOS 6. When I do a DBB to disk or to tape I'm seeing the following below messages in /var/log/message. The dbb's run successfully and as a low level software engineer I understand why it's happening; tsm is off in the weeds mucking about with the db and not responding to anything else. But, my concern is more along the lines of is this going to be a problem somewhere else; or is it indicative of some other problem that I'm not (yet) aware of.

Or, is this normal and not to be worried about?

thanks,

-b

Dec 18 09:18:21 tsm32 /usr/sbin/bmc-watchdog[3283]: Reset Watchdog Timer: driver timeout
Dec 18 09:22:57 tsm32 kernel: INFO: task dsmserv:27573 blocked for more than 120 seconds.
Dec 18 09:22:57 tsm32 kernel:      Tainted: G           -- ------------  T 2.6.32-573.8.1.el6.x86_64 #1
Dec 18 09:22:57 tsm32 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 18 09:22:57 tsm32 kernel: dsmserv       D ffff88053641c824     0 27573  30090 0x10000080
Dec 18 09:22:57 tsm32 kernel: ffff8802569cfdc8 0000000000000082 ffff8802569cfd78 00000000ffffffff
Dec 18 09:22:57 tsm32 kernel: ffff8802569cfd58 0000000000000001 00000000ffffffea 0000000000000000
Dec 18 09:22:57 tsm32 kernel: ffff8802569cfda8 ffffffff810b56a3 ffff8802792d9ad8 ffff8802569cffd8
Dec 18 09:22:57 tsm32 kernel: Call Trace:
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810b56a3>] ? futex_wake+0x93/0x150
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810a178e>] ? prepare_to_wait+0x4e/0x80
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0115595>] jbd2_log_wait_commit+0xc5/0x140 [jbd2]
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810a1460>] ? autoremove_wake_function+0x0/0x40
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0115928>] jbd2_complete_transaction+0x68/0xb0 [jbd2]
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0131061>] ext4_sync_file+0x121/0x1d0 [ext4]
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81104713>] ? trace_nowake_buffer_unlock_commit+0x43/0x60
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811c4611>] vfs_fsync_range+0xa1/0x100
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811c46dd>] vfs_fsync+0x1d/0x20
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811c471e>] do_fsync+0x3e/0x60
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811c4770>] sys_fsync+0x10/0x20
Dec 18 09:22:57 tsm32 kernel: [<ffffffff8100b2e8>] tracesys+0xd9/0xde
Dec 18 09:22:57 tsm32 kernel: INFO: task dsmserv:15286 blocked for more than 120 seconds.
Dec 18 09:22:57 tsm32 kernel:      Tainted: G           -- ------------  T 2.6.32-573.8.1.el6.x86_64 #1
Dec 18 09:22:57 tsm32 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 18 09:22:57 tsm32 kernel: dsmserv       D 0000000000000000     0 15286  30090 0x10000080
Dec 18 09:22:57 tsm32 kernel: ffff88028a86b9b8 0000000000000082 ffff88028a86b928 ffffffff8115cbfd
Dec 18 09:22:57 tsm32 kernel: ffff880238b72cc0 ffff88050fb50bb0 ffff88028a86b938 ffffffff8112734e
Dec 18 09:22:57 tsm32 kernel: 0000000000012840 0000000000000421 ffff880538a27068 ffff88028a86bfd8
Dec 18 09:22:57 tsm32 kernel: Call Trace:
Dec 18 09:22:57 tsm32 kernel: [<ffffffff8115cbfd>] ? page_add_new_anon_rmap+0x9d/0xf0
Dec 18 09:22:57 tsm32 kernel: [<ffffffff8112734e>] ? find_get_page+0x1e/0xa0
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810a178e>] ? prepare_to_wait+0x4e/0x80
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa010f09d>] do_get_write_access+0x29d/0x520 [jbd2]
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810a14e0>] ? wake_bit_function+0x0/0x50
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa010f471>] jbd2_journal_get_write_access+0x31/0x50 [jbd2]
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa015ce58>] __ext4_journal_get_write_access+0x38/0x80 [ext4]
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0136bb3>] ext4_reserve_inode_write+0x73/0xa0 [ext4]
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0136c2c>] ext4_mark_inode_dirty+0x4c/0x1d0 [ext4]
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa010e3d5>] ? jbd2_journal_start+0xb5/0x100 [jbd2]
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0136f20>] ext4_dirty_inode+0x40/0x60 [ext4]
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811be45b>] __mark_inode_dirty+0x3b/0x160
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811aeb42>] file_update_time+0xf2/0x170
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81129910>] __generic_file_aio_write+0x230/0x490
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81129bf8>] generic_file_aio_write+0x88/0x100
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0130e08>] ext4_file_write+0x58/0x190 [ext4]
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810b4e7c>] ? wake_futex+0x3c/0x60
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811917ba>] do_sync_write+0xfa/0x140
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810a1460>] ? autoremove_wake_function+0x0/0x40
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810ffdd2>] ? ring_buffer_lock_reserve+0xa2/0x160
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81104713>] ? trace_nowake_buffer_unlock_commit+0x43/0x60
Dec 18 09:22:57 tsm32 kernel: [<ffffffff812316c6>] ? security_file_permission+0x16/0x20
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81191ab8>] vfs_write+0xb8/0x1a0
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81192fcf>] ? fget_light_pos+0x3f/0x50
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811925f1>] sys_write+0x51/0xb0
Dec 18 09:22:57 tsm32 kernel: [<ffffffff8100b2e8>] tracesys+0xd9/0xde
Dec 18 09:22:57 tsm32 kernel: INFO: task db2sysc:30584 blocked for more than 120 seconds.
Dec 18 09:22:57 tsm32 kernel:      Tainted: G           -- ------------  T 2.6.32-573.8.1.el6.x86_64 #1
Dec 18 09:22:57 tsm32 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 18 09:22:57 tsm32 kernel: db2sysc       D ffff88023fc24b00     0 30584  30355 0x10000080
Dec 18 09:22:57 tsm32 kernel: ffff88012e493bb8 0000000000000086 0000000000000000 0000000000000001
Dec 18 09:22:57 tsm32 kernel: 000000000000000e ffff88012e493bd8 000343a6208b690c ffffffff81126ff0
Dec 18 09:22:57 tsm32 kernel: ffff88012e493b60 0000000136be9ec6 ffff88023751f068 ffff88012e493fd8
Dec 18 09:22:57 tsm32 kernel: Call Trace:
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81126ff0>] ? find_get_pages_tag+0x40/0x130
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0115595>] jbd2_log_wait_commit+0xc5/0x140 [jbd2]
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810a1460>] ? autoremove_wake_function+0x0/0x40
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0115928>] jbd2_complete_transaction+0x68/0xb0 [jbd2]
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0131061>] ext4_sync_file+0x121/0x1d0 [ext4]
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811c4611>] vfs_fsync_range+0xa1/0x100
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811c46bb>] generic_write_sync+0x4b/0x50
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81129c56>] generic_file_aio_write+0xe6/0x100
Dec 18 09:22:57 tsm32 kernel: [<ffffffffa0130e08>] ext4_file_write+0x58/0x190 [ext4]
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811917ba>] do_sync_write+0xfa/0x140
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810a1460>] ? autoremove_wake_function+0x0/0x40
Dec 18 09:22:57 tsm32 kernel: [<ffffffff810ffdd2>] ? ring_buffer_lock_reserve+0xa2/0x160
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81104713>] ? trace_nowake_buffer_unlock_commit+0x43/0x60
Dec 18 09:22:57 tsm32 kernel: [<ffffffff812316c6>] ? security_file_permission+0x16/0x20
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81191ab8>] vfs_write+0xb8/0x1a0
Dec 18 09:22:57 tsm32 kernel: [<ffffffff81192fcf>] ? fget_light_pos+0x3f/0x50
Dec 18 09:22:57 tsm32 kernel: [<ffffffff811925f1>] sys_write+0x51/0xb0
Dec 18 09:22:57 tsm32 kernel: [<ffffffff8100b2e8>] tracesys+0xd9/0xde
[root@tsm32 log]#

 

[moon-buddy]

These look like debug messages from the kernel more than anything else. I am not sure how to disable this. I believe that should not be an issue.

By the way, is the version of CentOS you are using a Beta release or a GA release? Beta releases might have debug turned on.

 

[BDMcGrew]

The OS is a GA release. Back in the days when I was young and stupid I'd use a beta on a production server but now I save the rawhide releases from my other desktop.

[root@tsm32 ~]# cat /etc/redhat-release
CentOS release 6.7 (Final)
[root@tsm32 ~]# uname -a
Linux tsm32 2.6.32-573.8.1.el6.x86_64 #1 SMP Tue Nov 10 18:01:38 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@tsm32 ~]#

I can turn the messages off, that's not a problem. Just wanted to make sure it wasn't indicative of some other low-level or inherent problem that might pop up at the least opportune time.