Today, our IMAP server has been struck by this bug. We're still running hardy and i'm aware that it is not supported since May 2013 but it's sad that this problem was not addressed before hardy EOL. Maybe it wasn't an easy task to backport the Jan 2009 fix mentioned in #7 to hardy kernel, too bad anyone tried to.
Data corruption is always bad, very bad business :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/294259 Title: XFS internal error xfs_trans_cancel at line 1164 of file /build/buildd/linux-2.6.27/fs/xfs/xfs_trans.c Status in “linux” package in Ubuntu: Won't Fix Bug description: Got this on my Intrepid (2.6.27-7) last night: Nov 4 17:25:55 pc kernel: [10142.198218] Filesystem "dm-25": XFS internal error xfs_trans_cancel at line 1164 of file /build/buildd/linux-2.6.27/fs/xfs/xfs_trans.c. Caller 0xf95840c9 Nov 4 17:25:56 pc kernel: [10142.198240] Pid: 22487, comm: rsync Tainted: P 2.6.27-7-generic #1 Nov 4 17:25:56 pc kernel: [10142.198267] [<f955cbc3>] xfs_error_report+0x53/0x60 [xfs] Nov 4 17:25:56 pc kernel: [10142.198358] [<f95840c9>] ? xfs_link+0x159/0x2d0 [xfs] Nov 4 17:25:56 pc kernel: [10142.198384] [<f957d4e2>] xfs_trans_cancel+0xd2/0xf0 [xfs] Nov 4 17:25:56 pc kernel: [10142.198442] [<f95840c9>] ? xfs_link+0x159/0x2d0 [xfs] Nov 4 17:25:56 pc kernel: [10142.198465] [<f95840c9>] xfs_link+0x159/0x2d0 [xfs] Nov 4 17:25:56 pc kernel: [10142.198484] [<c01c6a59>] ? __iget+0x9/0x60 Nov 4 17:25:56 pc kernel: [10142.198508] [<f958f793>] xfs_vn_link+0x43/0xa0 [xfs] Nov 4 17:25:56 pc kernel: [10142.198543] [<c01bb81c>] vfs_link+0xfc/0x170 Nov 4 17:25:56 pc kernel: [10142.198546] [<c01bd908>] sys_linkat+0xf8/0x110 Nov 4 17:25:56 pc kernel: [10142.198550] [<c01b5df7>] ? sys_lstat64+0x27/0x30 Nov 4 17:25:56 pc kernel: [10142.198557] [<c01781a4>] ? __report_bad_irq+0x14/0xa0 Nov 4 17:25:56 pc kernel: [10142.198564] [<c01bd955>] sys_link+0x35/0x40 Nov 4 17:25:56 pc kernel: [10142.198567] [<c0103f7b>] sysenter_do_call+0x12/0x2f Nov 4 17:25:56 pc kernel: [10142.198572] ======================= Nov 4 17:25:56 pc kernel: [10142.198576] xfs_force_shutdown(dm-25,0x8) called from line 1165 of file /build/buildd/linux-2.6.27/fs/xfs/xfs_trans.c. Return address = 0xf957d4fa Nov 4 17:25:56 pc kernel: [10142.199754] Filesystem "dm-25": Corruption of in-memory data detected. Shutting down filesystem: dm-25 Nov 4 17:25:56 pc kernel: [10142.199761] Please umount the filesystem, and rectify the problem(s) Nov 4 17:25:56 pc kernel: [10142.376160] Filesystem "dm-25": xfs_log_force: error 5 returned. I did unmount the fileystems and xfs_repair'd it, which advised that I remount to replay the log and then try to repair again which I did and after some number of minutes the filesystem was fixed and I could remount it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/294259/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
