Syslog 产生数百行

Question

我最近被“提升”为实验室管理员，因为我在 linux 方面拥有最多的经验。我的日志检查不断向我发送来自我的syslog文件的数百行电子邮件。它会不断重复，每次都有细微的变化。我不知道它想告诉我什么。有任何想法吗？这是一个重复的片段：

Aug 23 15:02:30 157-london kernel: [8747161.509412] ------------[ cut here ]------------
Aug 23 15:02:30 157-london kernel: [8747161.509416] WARNING: at /build/buildd-linux-2.6_2.6.32-45-amd64-FcX7RM/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/fs-writeback.c:588 writeback_inodes_wb+0x36b/0x4ff()
Aug 23 15:02:30 157-london kernel: [8747161.509419] Hardware name: Precision WorkStation 380    
Aug 23 15:02:30 157-london kernel: [8747161.509421] Modules linked in: nls_utf8 cifs xt_multiport nfsd nfs lockd fscache nfs_acl auth_rpcgss sunrpc xt_tcpudp iptable_filter ip_tables x_tables ext3 jbd mbcache raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx quota_v2 quota_tree firewire_sbp2 loop md_mod nouveau ttm i2c_i801 drm_kms_helper drm i2c_algo_bit parport_pc i2c_core parport dcdbas snd_ctxfi snd_pcm rng_core pcspkr button evdev snd_timer psmouse snd soundcore snd_page_alloc processor serio_raw xfs exportfs usbhid hid sg sr_mod cdrom sd_mod crc_t10dif ata_generic uhci_hcd ehci_hcd firewire_ohci aic79xx thermal ahci ata_piix tg3 firewire_core crc_itu_t scsi_transport_spi floppy thermal_sys usbcore nls_base libata scsi_mod libphy [last unloaded: scsi_wait_scan]
Aug 23 15:02:30 157-london kernel: [8747161.509477] Pid: 22965, comm: flush-9:0 Tainted: G        W  2.6.32-5-amd64 #1
Aug 23 15:02:30 157-london kernel: [8747161.509479] Call Trace:
Aug 23 15:02:30 157-london kernel: [8747161.509482]  [<ffffffff81109027>] ? writeback_inodes_wb+0x36b/0x4ff
Aug 23 15:02:30 157-london kernel: [8747161.509485]  [<ffffffff81109027>] ? writeback_inodes_wb+0x36b/0x4ff
Aug 23 15:02:30 157-london kernel: [8747161.509489]  [<ffffffff8104df40>] ? warn_slowpath_common+0x77/0xa3
Aug 23 15:02:30 157-london kernel: [8747161.509492]  [<ffffffff81109027>] ? writeback_inodes_wb+0x36b/0x4ff
Aug 23 15:02:30 157-london kernel: [8747161.509496]  [<ffffffff811092e7>] ? wb_writeback+0x12c/0x1ab
Aug 23 15:02:30 157-london kernel: [8747161.509499]  [<ffffffff81109481>] ? wb_do_writeback+0x73/0x165
Aug 23 15:02:30 157-london kernel: [8747161.509516]  [<ffffffff810c934c>] ? bdi_start_fn+0xbc/0xd0
Aug 23 15:02:30 157-london kernel: [8747161.509521]  [<ffffffff810c9290>] ? bdi_start_fn+0x0/0xd0
Aug 23 15:02:30 157-london kernel: [8747161.509524]  [<ffffffff81064d75>] ? kthread+0x79/0x81
Aug 23 15:02:30 157-london kernel: [8747161.509528]  [<ffffffff81011baa>] ? child_rip+0xa/0x20
Aug 23 15:02:30 157-london kernel: [8747161.509531]  [<ffffffff81064cfc>] ? kthread+0x0/0x81
Aug 23 15:02:30 157-london kernel: [8747161.509534]  [<ffffffff81011ba0>] ? child_rip+0x0/0x20
Aug 23 15:02:30 157-london kernel: [8747161.509536] ---[ end trace 7157c19847c3ced3 ]---

Answer 1

您看到的是堆栈跟踪。这是一个来自内核的未处理错误，显示了当某些事情出现如此该死的错误时的执行路径，除了记录问题并将其留给人类解决之外别无他法。

头部的调用通常是定义性的：

WARNING: at /build/buildd-linux-2.6_2.6.32-45-amd64-FcX7RM/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/fs-writeback.c:588 writeback_inodes_wb+0x36b/0x4ff()

fs-writeback: 那是写入文件系统。正如在对您的问题的评论中指出的那样，您的磁盘上可能有错误。我首先将机器以只读方式安装到单用户模式并运行fsck.