On Wed, Aug 16, 2006 at 02:03:48PM +0200, Fredrik Olofsson wrote: > Package: linux-image-2.6.17-2-686 > Version: 2.6.17-6 > Severity: important > > After booting the kernel from linux-image-2.6.17-2 2.6.17-6 one of my > xfs partitions stopped working (the system was idle at the time of the > error). Dmesg contained the following error: > > Filesystem "hda3": XFS internal error xfs_trans_cancel at line 1150 of file > fs/xfs/xfs_trans.c. Caller 0xd0933588 > <d093542e> xfs_trans_cancel+0x4d/0xd6 [xfs] <d0933588> > xfs_rename+0xa23/0xacf [xfs] > <d0933588> xfs_rename+0xa23/0xacf [xfs] <d094590d> xfs_vn_rename+0x24/0x64 > [xfs] > <d0924fed> xfs_iaccess+0x7c/0x146 [xfs] <d093a876> xfs_access+0x34/0x3a > [xfs] > <d094594d> xfs_vn_permission+0x0/0x13 [xfs] <d094595c> > xfs_vn_permission+0xf/0x13 [xfs] > <b0142a17> kstrdup+0x23/0x42 <b015e819> vfs_rename+0x29c/0x3dc > <b015eb5e> __lookup_hash+0x4a/0xc5 <b0160213> sys_renameat+0x155/0x1b9 > <b0160288> sys_rename+0x11/0x15 <b0102ae7> sysenter_past_esp+0x54/0x75 > xfs_force_shutdown(hda3,0x8) called from line 1151 of file > fs/xfs/xfs_trans.c. Return address = 0xd0948200 > Filesystem "hda3": Corruption of in-memory data detected. Shutting down > filesystem: hda3 > Please umount the filesystem, and rectify the problem(s) > > This computer has shown no problems for a long before booting this > kernel. The computer contains a 1.7GHz P4 and 512MB memory. Also, I had > the nvidia kernel module loaded.. > > After rebooting to linux-image-2.6.17-1 2.6.17-5 the filesystem seems to > work with no problems again.
Frederik, I see nothing in 2.6.17-6 that looks like it could reasonably cause this - but there was an XFS corruption bug that was fixed in 2.6.17-5. Did you ever mount this fs with an earlier 2.6.17 kernel? I would suggest forcing a run of xfs_repair on your fs, and retrying 2.6.17-6. Please let us know how that works for you. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
