Bug#383299: marked as done (linux-image-2.6.17-2-686: 2.6.17-2 XFS error)
Your message dated Thu, 17 Aug 2006 11:57:58 +0200
with message-id <20060817095758.GJ4868@baikonur.stro.at>
and subject line Bug#383299: linux-image-2.6.17-2-686: 2.6.17-2 XFS error
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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.
Thanks
/Fredrik
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.17-2-686 depends on:
ii module-init-tools 3.2.2-3 tools for managing Linux kernel mo
ii yaird [linux-initramfs-tool] 0.0.12-17 Yet Another mkInitRD
Versions of packages linux-image-2.6.17-2-686 recommends:
ii libc6-i686 2.3.6-19 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true
linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686:
linux-image-2.6.17-2-686/postinst/really-run-bootloader-2.6.17-2-686: true
linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false
linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true
linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686:
linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk:
linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686:
linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686:
linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true
linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686:
linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686:
linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true
linux-image-2.6.17-2-686/postinst/kimage-is-a-directory:
linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true
linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true
linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false
linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686:
--- End Message ---
--- Begin Message ---
On Thu, Aug 17, 2006 at 10:23:45AM +0200, Fredrik Olofsson wrote:
>
>
> Feel free to close this bug as user error or something.
by mailing to bugnr-done@bugs.debian.org that is done,
doing as the xfs trouble happened earlier.
> Now I only have to find out "the Debian way" of getting a root shell
> before / is remounted read-write so I can check that filesystem as
> well...
boot into single user mode by either appending 1 or single
on the boot line, kernel args are the same across distributions.
best regards
--
maks
--- End Message ---
Reply to: