Your message dated Thu, 10 Aug 2006 20:47:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#382394: XFS corruption
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-1-powerpc
Version: 2.6.17-5
Severity: important
Today I got a file system crash that completely screwed up my laptop. It
happened during an upgrade of unstable after 10 days from the previous
upgrade. Probably one of the file system went full and the file system
crashed.
This is what I read on the screen:
xfs_da_do_buf: bno 16777216
dir: inode 8852516
Filesystem "dm-2": XFS internal error xfs_do_da_buf(1) at line 2119 of
file fs/xfs/xfs_da_btree.c. Caller 0xf26c8d60
Call Trace:
[EFD05BE0] [C00078AC] show_stack+0x53/0x174 (unreliable)
[EFD05C10] [F26D7444] xfs_error_report+0x4c/0x5c [xfs]
[EFD05C20] [F26C8944] xfs_da_do_buf+0x3e4/0x778 [xfs]
[EFD05CB0] [F26C8D60] xfs_da_read_buf+0x2c/0x3c [xfs]
[EFD05CC0] [F26D1DC0] xfs_dir2_node_removename+0x1e8/0x408 [xfs]
[EFD05D20] [F26CCA84] xfs_dir2_removename+0x10c/0x120 [xfs]
[EFD05DB0] [F26FACE8] xfs_remove+0x280/0x42c [xfs]
[EFD05E20] [F270541C] xfs_vn_unlink+0x30/0x68 [xfs]
[EFD05EB0] [C0083B40] vfs_unlink+0xe8/0x134
[EFD05ED0] [C0085E08] do_unlinkat+0xcc/0x158
[EFD05F40] [C0010A24] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff5c468
LR = 0x10012c08
Filesystem "dm-2": XFS internal error xfs_trans_cancel at line 1150 of
file fs/xfs/xfs_trans.c. Caller 0xf26fae60
Call Trace:
[EFD05D50] [C00078AC] show_stack+0x54/0x174 (unreliable)
[EFD05D80] [F26D7444] xfs_error_report+0x4c/0x5c [xfs]
[EFD05D90] [F26F1A8C] xfs_trans_cancel+0x7c/0x118 [xfs]
[EFD05DB0] [F26FAE60] xfs_remove+0x3f8/0x42c [xfs]
[EFD05E20] [F270541C] xfs_vn_unlink+0x30/0x68 [xfs]
[EFD05EB0] [C0083B40] vfs_unlink+0xe8/0x134
[EFD05ED0] [C0085E08] do_unlinkat+0xcc/0x158
[EFD05F40] [C0010A24] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff5c468
LR = 0x10012c08
xfs_force_shutdown(dm-2,0x8) called from line 1151 of file
fs/xfs/xfs_trans.c. Caller 0xf2708b04
Filesystem "dm-2": Corruption of in-memory data detected. Shutting down
filesystem: dm-2
Please umount the filesystem, and rectify the problem(s)
dpkg: error processing libx11-dev (--remove):
cannot remove file
`/usr/share/man/man3/XTextPropertyToStringList.3.gz': Not a directory
Errors were encountered while processing:
libx11-dev
E: Sub-process /usr/bin/dpkg returned an error code (1)
eppesuig3:~# umount /usr
xfs_force_shutdown(dm-2,0x1) called from line 338 of file
fs/xfs/xfs_rw.c. Return address = 0xf2708b4
xfs_force_shutdown(dm-2,0x1) called from line 338 of file
fs/xfs/xfs_rw.c. Return address = 0xf2708b4
The prompt did not returned, so I powered off the machine and restarted
it in single user. Then I used xfs_repair of all my xfs volumes (/var
and /usr) but the /usr volume cannot be mounted even after xfs_repair
fix it.
Every kind of access the the /usr file system give this error:
0x0: 09 20 20 20 47 64 6b 43 6f 6c 6f 72 20 20 20 20
Filesystem "dm-2": XFS internal error xfs_da_do_buf(2) at line 2212 of
file fs/xfs/xfs_btree.c. Caller 0xf26cbd60
Call Trace:
[........] [........] show_stack+0x54/0x174 (unreliable)
[........] [........] xfs_error_report+0x4c/0x5c [xfs]
[........] [........] xfs_corruption_error+0x104/0x118 [xfs]
[........] [........] xfs_da_do_buf+0x6a0/0x778 [xfs]
[........] [........] xfs_da_read_buf+0x2c/0x3c [xfs]
[........] [........] xfs_da_node_lookup_int+0x90/0x358 [xfs]
[........] [........] xfs_dir2_node_lookup+0x44/0xcc [xfs]
[........] [........] xfs_dir2_lookup+0x100/0x13c [xfs]
[........] [........] xfs_dir_lookup_int+0x44/0x100 [xfs]
[........] [........] xfs_lookup+0x60/0x98 [xfs]
[........] [........] xfs_vn_lookup+0x50/0xac [xfs]
[........] [........] do_lookup+0xc0/0x18c
[........] [........] __link_path_walk+0x918/0xe8c
[........] [........] link_path_walk+0x80/0x144
[........] [........] do_path_lookup+0x218/0x24c
[........] [........] __path_lookup_intent_open+0x58/0xa4
[........] [........] open_namei+0x6c/0x694
[........] [........] do_filp_open+0x2c/0x5c
[........] [........] do_sys_open+0x58/0xf4
[........] [........] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0x30012c08
LR = 0x300055c4
Bye,
Giuseppe
--- End Message ---
--- Begin Message ---
On Thu, Aug 10, 2006 at 06:58:23PM +0200, Giuseppe Sacco wrote:
> Today I got a file system crash that completely screwed up my laptop. It
> happened during an upgrade of unstable after 10 days from the previous
> upgrade. Probably one of the file system went full and the file system
> crashed.
Versions between 2.6.17-1 and 2.6.17-4 contains a known bug. Use
xfs_repair.
Bastian
--
Actual war is a very messy business. Very, very messy business.
-- Kirk, "A Taste of Armageddon", stardate 3193.0
--- End Message ---
