Script started on Tue 25 May 2010 11:07:52 AM CEST root@xen:~# e2fsck -v /dev/mapper/vault e2fsck 1.40.8 (13-Mar-2008) /dev/mapper/vault contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes 1168476 inodes used (1.91%) 10047 non-contiguous inodes (0.9%) # of inodes with ind/dind/tind blocks: 54816/15969/1 184001769 blocks used (75.36%) 0 bad blocks 4 large files 455997 regular files 708469 directories 0 character device files 0 block device files 0 fifos 4023768 links 4001 symbolic links (3257 fast symbolic links) 0 sockets -------- 5192235 files root@xen:~# echo $? 0 root@xen:~# mount /mnt/vault/ root@xen:~# tail /var/log/messages May 25 11:33:59 xen rsyslogd:-- MARK -- May 25 11:38:59 xen rsyslogd:-- MARK -- May 25 11:40:21 xen kernel: [245838.693465] firewire_core: Unsolicited response (source ffc0, tlabel e) May 25 11:43:59 xen rsyslogd:-- MARK -- May 25 11:48:59 xen rsyslogd:-- MARK -- May 25 11:53:59 xen rsyslogd:-- MARK -- May 25 11:54:53 xen kernel: [246982.976055] kjournald starting. Commit interval 5 seconds May 25 11:54:53 xen kernel: [246663.474863] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure May 25 11:54:53 xen kernel: [246663.474868] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Marking fs in need of filesystem check. May 25 11:54:53 xen kernel: [246663.479941] EXT3-fs: mounted filesystem with ordered data mode. root@xen:~# umount /mnt/vault root@xen:~# tail /var/log/messages May 25 11:33:59 xen rsyslogd:-- MARK -- May 25 11:38:59 xen rsyslogd:-- MARK -- May 25 11:40:21 xen kernel: [245838.693465] firewire_core: Unsolicited response (source ffc0, tlabel e) May 25 11:43:59 xen rsyslogd:-- MARK -- May 25 11:48:59 xen rsyslogd:-- MARK -- May 25 11:53:59 xen rsyslogd:-- MARK -- May 25 11:54:53 xen kernel: [246982.976055] kjournald starting. Commit interval 5 seconds May 25 11:54:53 xen kernel: [246663.474863] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure May 25 11:54:53 xen kernel: [246663.474868] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Marking fs in need of filesystem check. May 25 11:54:53 xen kernel: [246663.479941] EXT3-fs: mounted filesystem with ordered data mode. root@xen:~# mount /mnt/vault/ root@xen:~# tail /var/log/messages May 25 11:48:59 xen rsyslogd:-- MARK -- May 25 11:53:59 xen rsyslogd:-- MARK -- May 25 11:54:53 xen kernel: [246982.976055] kjournald starting. Commit interval 5 seconds May 25 11:54:53 xen kernel: [246663.474863] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure May 25 11:54:53 xen kernel: [246663.474868] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Marking fs in need of filesystem check. May 25 11:54:53 xen kernel: [246663.479941] EXT3-fs: mounted filesystem with ordered data mode. May 25 11:55:29 xen kernel: [247014.694416] kjournald starting. Commit interval 5 seconds May 25 11:55:29 xen kernel: [246694.090307] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure May 25 11:55:29 xen kernel: [246694.090311] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Marking fs in need of filesystem check. May 25 11:55:29 xen kernel: [246694.094338] EXT3-fs: mounted filesystem with ordered data mode. Script done on Tue 25 May 2010 11:55:39 AM CEST ================ /var/log/messages ================= May 25 03:30:43 xen kernel: [217621.254486] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK May 25 03:30:43 xen kernel: [217621.254495] end_request: I/O error, dev sdb, sector 366464538 May 25 03:30:43 xen kernel: [217621.257871] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK May 25 03:30:43 xen kernel: [217621.257875] end_request: I/O error, dev sdb, sector 12274 May 25 03:30:43 xen kernel: [217621.257894] lost page write due to I/O error on dm-31 May 25 03:30:43 xen kernel: [217621.258662] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK May 25 03:30:43 xen kernel: [217621.258666] end_request: I/O error, dev sdb, sector 1962 May 25 03:30:43 xen kernel: [217621.258681] lost page write due to I/O error on dm-31 May 25 03:30:43 xen kernel: [217621.258981] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK May 25 03:30:43 xen kernel: [217621.258984] end_request: I/O error, dev sdb, sector 366464538 May 25 03:30:43 xen kernel: [217621.265704] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK May 25 03:30:43 xen kernel: [217621.265711] end_request: I/O error, dev sdb, sector 408129594 May 25 03:30:43 xen kernel: [217621.268752] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK May 25 03:30:43 xen kernel: [217621.268757] end_request: I/O error, dev sdb, sector 408129594 May 25 03:30:43 xen kernel: [217621.269935] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK May 25 03:30:43 xen kernel: [217621.269939] end_request: I/O error, dev sdb, sector 408129594 May 25 03:30:43 xen kernel: [217782.363955] __journal_remove_journal_head: freeing b_committed_data May 25 10:58:59 xen rsyslogd:-- MARK -- May 25 11:00:03 xen kernel: [243662.457032] clocksource/0: Time went backwards: ret=df8da74cc802 delta=-21800816 shadow=df8d8f78fd02 offset=1923c6f7 May 25 11:01:03 xen kernel: [243983.560543] kjournald starting. Commit interval 5 seconds May 25 11:01:03 xen kernel: [243707.464339] EXT3-fs: mounted filesystem with ordered data mode. May 25 11:01:18 xen kernel: [243722.098543] __journal_remove_journal_head: freeing b_committed_data May 25 11:01:18 xen kernel: [243722.098794] __journal_remove_journal_head: freeing b_committed_data May 25 11:01:18 xen kernel: [243722.099019] WARNING: at /data/Scratch/scm/hardy-git/debian/build/custom-source-xen/fs/buffer.c:1169 mark_buffer_dirty() May 25 11:01:18 xen kernel: [243722.099023] Pid: 20378, comm: umount Not tainted 2.6.24-24-xen #1 May 25 11:01:18 xen kernel: [243722.099025] May 25 11:01:18 xen kernel: [243722.099025] Call Trace: May 25 11:01:18 xen kernel: [243722.099043] [] mark_buffer_dirty+0x87/0xa0 May 25 11:01:18 xen kernel: [243722.099051] [] :jbd:journal_update_superblock+0x82/0x100 May 25 11:01:18 xen kernel: [243722.099058] [] :jbd:journal_destroy+0x18c/0x1f0 May 25 11:01:18 xen kernel: [243722.099063] [] autoremove_wake_function+0x0/0x30 May 25 11:01:18 xen kernel: [243722.099076] [] :ext3:ext3_put_super+0x29/0x210 May 25 11:01:18 xen kernel: [243722.099080] [] generic_shutdown_super+0x6a/0x120 May 25 11:01:18 xen kernel: [243722.099082] [] kill_block_super+0xd/0x20 May 25 11:01:18 xen kernel: [243722.099084] [] deactivate_super+0x74/0xb0 May 25 11:01:18 xen kernel: [243722.099088] [] sys_umount+0x6b/0x2f0 May 25 11:01:18 xen kernel: [243722.099092] [] sys_newstat+0x27/0x50 May 25 11:01:18 xen kernel: [243722.099096] [] do_munmap+0x2de/0x340 May 25 11:01:18 xen kernel: [243722.099100] [] __up_write+0x21/0x150 May 25 11:01:18 xen kernel: [243722.099105] [] system_call+0x68/0x6d May 25 11:01:18 xen kernel: [243722.099108] [] system_call+0x0/0x6d May 25 11:01:18 xen kernel: [243722.099111] May 25 11:01:25 xen kernel: [243728.778697] EXT3-fs: INFO: recovery required on readonly filesystem. May 25 11:01:25 xen kernel: [243728.778705] EXT3-fs: write access will be enabled during recovery. May 25 11:01:25 xen kernel: [244004.953361] kjournald starting. Commit interval 5 seconds May 25 11:01:25 xen kernel: [243728.787116] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure May 25 11:01:25 xen kernel: [243728.787134] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Marking fs in need of filesystem check. May 25 11:01:25 xen kernel: [243728.792231] EXT3-fs: recovery complete. May 25 11:01:25 xen kernel: [243728.796223] EXT3-fs: mounted filesystem with ordered data mode. May 25 11:03:59 xen rsyslogd:-- MARK -- May 25 11:08:59 xen rsyslogd:-- MARK -- May 25 11:13:59 xen rsyslogd:-- MARK -- May 25 11:18:59 xen rsyslogd:-- MARK -- May 25 11:23:59 xen rsyslogd:-- MARK -- May 25 11:25:07 xen kernel: [245027.295287] applesmc: wait status failed: 4 != 15 May 25 11:25:07 xen kernel: [245027.297909] applesmc: wait status failed: c != 18 May 25 11:28:59 xen rsyslogd:-- MARK -- May 25 11:33:59 xen rsyslogd:-- MARK -- May 25 11:38:59 xen rsyslogd:-- MARK -- May 25 11:40:21 xen kernel: [245838.693465] firewire_core: Unsolicited response (source ffc0, tlabel e) May 25 11:43:59 xen rsyslogd:-- MARK -- May 25 11:48:59 xen rsyslogd:-- MARK -- May 25 11:53:59 xen rsyslogd:-- MARK -- May 25 11:54:53 xen kernel: [246982.976055] kjournald starting. Commit interval 5 seconds May 25 11:54:53 xen kernel: [246663.474863] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure May 25 11:54:53 xen kernel: [246663.474868] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Marking fs in need of filesystem check. May 25 11:54:53 xen kernel: [246663.479941] EXT3-fs: mounted filesystem with ordered data mode. May 25 11:55:29 xen kernel: [247014.694416] kjournald starting. Commit interval 5 seconds May 25 11:55:29 xen kernel: [246694.090307] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure May 25 11:55:29 xen kernel: [246694.090311] EXT3-fs warning (device dm-31): ext3_clear_journal_err: Marking fs in need of filesystem check. May 25 11:55:29 xen kernel: [246694.094338] EXT3-fs: mounted filesystem with ordered data mode. May 25 11:58:59 xen rsyslogd:-- MARK -- May 25 12:04:00 xen rsyslogd:-- MARK -- May 25 12:05:18 xen kernel: [247567.972858] applesmc: wait status failed: 4 != 15 May 25 12:05:18 xen kernel: [247567.975447] applesmc: wait status failed: c != 18 May 25 12:09:00 xen rsyslogd:-- MARK -- May 25 12:14:00 xen rsyslogd:-- MARK -- May 25 12:19:00 xen rsyslogd:-- MARK -- May 25 12:24:00 xen rsyslogd:-- MARK --