Just got same error here after upgrading to 2.6.31-22 kernel. The machine is a
KVM virtual guest and has been running well for a couple months with no issues.
While rsync'ing from the host over ssh, I got:
Corruption of in-memory data detected
grep BOOT syslog
===================================================================================================
Jun 4 14:33:05 wolfgang kernel: [ 0.000000] Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.31-22-server root=/dev/vda1 ro clocksource=pit
Jun 4 14:33:05 server01 kernel: [ 0.000000] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.31-22-server root=/dev/vda1 ro clocksource=pit
Jun 4 14:33:05 server01 kernel: [ 0.000000] Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.31-22-server root=/dev/vda1 ro clocksource=pit
kern.log
===================================================================================================
Jun 4 20:40:30 server01 kernel: [ 4069.541276] XFS internal error
XFS_WANT_CORRUPTED_GOTO at line 1629 of file
/build/buildd/linux-2.6.31/fs/xfs/xfs_alloc.c. Caller 0xffffffffa0046494
Jun 4 20:40:30 server01 kernel: [ 4069.544918] Pid: 1924, comm: xauth Not
tainted 2.6.31-22-server #60-Ubuntu
Jun 4 20:40:30 server01 kernel: [ 4069.544925] Call Trace:
Jun 4 20:40:30 server01 kernel: [ 4069.545124] [<ffffffffa006ba2e>]
xfs_error_report+0x3e/0x40 [xfs]
Jun 4 20:40:30 server01 kernel: [ 4069.545188] [<ffffffffa0046494>] ?
xfs_free_extent+0xb4/0xe0 [xfs]
Jun 4 20:40:30 server01 kernel: [ 4069.545230] [<ffffffffa0044a3d>]
xfs_free_ag_extent+0x51d/0x670 [xfs]
Jun 4 20:40:30 server01 kernel: [ 4069.545264] [<ffffffffa0046494>]
xfs_free_extent+0xb4/0xe0 [xfs]
Jun 4 20:40:30 server01 kernel: [ 4069.545301] [<ffffffffa00510fd>]
xfs_bmap_finish+0x15d/0x1a0 [xfs]
Jun 4 20:40:30 server01 kernel: [ 4069.545358] [<ffffffffa0072dd9>]
xfs_itruncate_finish+0x169/0x340 [xfs]
Jun 4 20:40:30 server01 kernel: [ 4069.545420] [<ffffffffa008d4a6>]
xfs_inactive+0x346/0x4a0 [xfs]
Jun 4 20:40:30 server01 kernel: [ 4069.545508] [<ffffffff8115248c>] ?
fsnotify_clear_marks_by_inode+0x9c/0x100
Jun 4 20:40:30 server01 kernel: [ 4069.545566] [<ffffffffa009a12d>]
xfs_fs_clear_inode+0x6d/0x70 [xfs]
Jun 4 20:40:30 server01 kernel: [ 4069.545614] [<ffffffff811354f9>]
clear_inode+0x79/0xf0
Jun 4 20:40:30 server01 kernel: [ 4069.545626] [<ffffffff81135eb6>]
generic_delete_inode+0x176/0x1a0
Jun 4 20:40:30 server01 kernel: [ 4069.545634] [<ffffffff81135f05>]
generic_drop_inode+0x25/0x30
Jun 4 20:40:30 server01 kernel: [ 4069.545641] [<ffffffff8113492d>]
iput+0x5d/0x70
Jun 4 20:40:30 server01 kernel: [ 4069.545660] [<ffffffff8112c19a>]
do_unlinkat+0x10a/0x1d0
Jun 4 20:40:30 server01 kernel: [ 4069.545702] [<ffffffff8127c096>] ?
__up_write+0xd6/0x140
Jun 4 20:40:30 server01 kernel: [ 4069.545714] [<ffffffff8112c271>]
sys_unlink+0x11/0x20
Jun 4 20:40:30 server01 kernel: [ 4069.545754] [<ffffffff81012042>]
system_call_fastpath+0x16/0x1b
Jun 4 20:40:30 server01 kernel: [ 4069.545787] xfs_force_shutdown(vda1,0x8)
called from line 4341 of file /build/buildd/linux-2.6.31/fs/xfs/xfs_bmap.c.
Return address = 0xffffffffa0051136
Jun 4 20:40:30 server01 kernel: [ 4069.547176] Filesystem "vda1": Corruption
of in-memory data detected. Shutting down filesystem: vda1
Jun 4 20:40:30 server01 kernel: [ 4069.549650] Please umount the filesystem,
and rectify the problem(s)
Jun 4 20:40:53 server01 kernel: [ 4092.520210] Filesystem "vda1":
xfs_log_force: error 5 returned.
reboot to cd, mount vdaX on /mnt/slash
===================================================================================================
r...@ubuntu:/mnt# mount /dev/vda1 slash
mount: Structure needs cleaning
r...@ubuntu:/mnt# xfs_check /dev/vda1
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_check. If you are unable to mount the filesystem, then use
the xfs_repair -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
r...@ubuntu:/mnt# mount /dev/vda1 slash
mount: Structure needs cleaning
r...@ubuntu:/mnt# xfs_repair -L /dev/vda1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
destroyed because the -L option was used.
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
7f0594189910: Badness in key lookup (length)
bp=(bno 560, len 16384 bytes) key=(bno 560, len 8192 bytes)
imap claims a free inode 565 is in use, correcting imap and clearing inode
cleared inode 565
imap claims a free inode 299985 is in use, correcting imap and clearing inode
cleared inode 299985
- agno = 1
7f0591984910: Badness in key lookup (length)
bp=(bno 2125408, len 16384 bytes) key=(bno 2125408, len 8192 bytes)
7f0591984910: Badness in key lookup (length)
bp=(bno 2139312, len 16384 bytes) key=(bno 2139312, len 8192 bytes)
- agno = 2
imap claims a free inode 8458466 is in use, correcting imap and clearing inode
cleared inode 8458466
- agno = 3
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
entry ".viminfo" at block 0 offset 1648 in directory inode 140 references free
inode 299985
clearing inode number in entry at offset 1648...
- agno = 2
- agno = 3
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
bad hash table for directory inode 140 (no data entry): rebuilding
rebuilding directory inode 140
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 1141, moving to lost+found
disconnected inode 8430681, moving to lost+found
disconnected inode 8430692, moving to lost+found
disconnected inode 8430696, moving to lost+found
disconnected inode 8430700, moving to lost+found
disconnected inode 8430716, moving to lost+found
disconnected inode 8458464, moving to lost+found
disconnected inode 8458467, moving to lost+found
disconnected inode 8458487, moving to lost+found
disconnected inode 8458490, moving to lost+found
disconnected inode 8458491, moving to lost+found
disconnected inode 8458505, moving to lost+found
Phase 7 - verify and correct link counts...
done
--
XFS kernel bug in ami-7e28ca17?
https://bugs.launchpad.net/bugs/504386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
