From: Callan Tham <callan.tham@securecirt.com>
To: linux-kernel@vger.kernel.org
Subject: Possible XFS Corruption
Date: Mon, 02 Aug 2004 11:49:05 +0800 [thread overview]
Message-ID: <1091418545.6750.12.camel@taz.lan.securecirt.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]
Hi list,
I'm running a Gentoo-patched 2.6.7 kernel, and am experiencing possible
XFS corruption on one of my partitions. I've included a sample of the
logs I've managed to see here:
Filesystem "hda1": XFS internal error xfs_da_do_buf(2) at line 2273 of
file fs/xfs/xfs_da_btree.c. Caller 0xc02420ec
[<c0241b2f>] xfs_da_do_buf+0x41f/0x960
[<c02420ec>] xfs_da_read_buf+0x3c/0x40
[<c02420ec>] xfs_da_read_buf+0x3c/0x40
[<c02420ec>] xfs_da_read_buf+0x3c/0x40
[<c0249611>] xfs_dir2_leaf_lookup_int+0x41/0x280
[<c0249611>] xfs_dir2_leaf_lookup_int+0x41/0x280
[<c0132a80>] do_generic_mapping_read+0x180/0x3a0
[<c02340e9>] xfs_bmap_last_offset+0xa9/0x120
[<c0249540>] xfs_dir2_leaf_lookup+0x20/0xb0
[<c02441f2>] xfs_dir2_lookup+0x112/0x130
[<c0132ca0>] file_read_actor+0x0/0xe0
[<c0283687>] xfs_read+0x197/0x250
[<c02736dc>] xfs_dir_lookup_int+0x2c/0xe0
[<c02781e7>] xfs_lookup+0x37/0x70
[<c0282aaa>] linvfs_lookup+0x4a/0x90
[<c015700f>] real_lookup+0xaf/0xd0
[<c0157218>] do_lookup+0x68/0x80
[<c0157628>] link_path_walk+0x3f8/0x7d0
[<c0157c06>] path_lookup+0x66/0x110
[<c015489f>] open_exec+0x1f/0xe0
[<c015499c>] kernel_read+0x3c/0x50
[<c016f8cf>] load_elf_binary+0xaef/0xb70
[<c011bd3d>] mm_init+0x8d/0xc0
[<c0135d52>] buffered_rmqueue+0xd2/0x180
[<c0135ead>] __alloc_pages+0xad/0x340
[<c013605b>] __alloc_pages+0x25b/0x340
[<c0291628>] __copy_from_user_ll+0x58/0x60
[<c0155411>] search_binary_handler+0x51/0x1a0
[<c015570b>] do_execve+0x1ab/0x230
[<c01049de>] sys_execve+0x2e/0x60
[<c0105d07>] syscall_call+0x7/0xb
This is not the first time I have seen this error, and am wondering if
it is something anyone has experienced regularly. Any help in diagnosing
this problem is greatly appreciated.
Please CC me any replies, as I'm not subscribed to the list at this
address. Thanks in advance!
Callan
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-08-02 3:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 3:49 Callan Tham [this message]
2004-08-02 5:02 ` Possible XFS Corruption Nathan Scott
2004-08-02 4:20 ` Callan Tham
2004-08-02 5:48 ` Nathan Scott
-- strict thread matches above, loose matches on Subject: below --
2010-12-07 11:49 possible xfs corruption blacknred
2010-12-07 14:10 ` Emmanuel Florac
2010-12-07 15:11 ` blacknred
2010-12-07 15:42 ` Emmanuel Florac
2010-12-07 17:30 ` blacknred
2010-12-07 18:15 ` Stan Hoeppner
2010-12-07 19:32 ` Michael Monnerie
2010-12-07 22:10 ` Dave Chinner
2010-12-09 3:44 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1091418545.6750.12.camel@taz.lan.securecirt.com \
--to=callan.tham@securecirt.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.