From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-xfs@oss.sgi.com
Subject: XFS Oops Under 2.6.12.2
Date: Sat, 9 Jul 2005 06:20:53 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0507090614290.21767@p34> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1491 bytes --]
After a couple hours of use, I get this error on a linear RAID under
2.6.12.2 using loop-AES w/AES-256 encrypted filesystem.
Anyone know what is wrong?
Filesystem "loop1": XFS internal error xfs_da_do_buf(2) at line 2271 of
file fs/xfs/xfs_da_btree.c. Caller 0xc025e807
[<c025e3f0>] xfs_da_do_buf+0x500/0x860
[<c025e807>] xfs_da_read_buf+0x57/0x60
[<c025e807>] xfs_da_read_buf+0x57/0x60
[<c03b70db>] __tcp_data_snd_check+0xcb/0xe0
[<c03b6ffd>] tcp_new_space+0x8d/0xa0
[<c03c0b55>] tcp_v4_rcv+0x585/0x810
[<c025e807>] xfs_da_read_buf+0x57/0x60
[<c0262224>] xfs_dir2_block_getdents+0xa4/0x330
[<c0262224>] xfs_dir2_block_getdents+0xa4/0x330
[<c03a51e0>] ip_local_deliver_finish+0x0/0x150
[<c03a5061>] ip_rcv+0x391/0x510
[<c02500f2>] xfs_bmap_last_offset+0xc2/0x120
[<c03a5330>] ip_rcv_finish+0x0/0x290
[<c0261570>] xfs_dir2_put_dirent64_direct+0x0/0xc0
[<c02614a2>] xfs_dir2_isblock+0x32/0x90
[<c0261570>] xfs_dir2_put_dirent64_direct+0x0/0xc0
[<c0260d11>] xfs_dir2_getdents+0xa1/0x150
[<c0261570>] xfs_dir2_put_dirent64_direct+0x0/0xc0
[<c029b365>] xfs_readdir+0x75/0xc0
[<c02a36de>] linvfs_readdir+0x10e/0x270
[<c03737ba>] net_rx_action+0x6a/0xf0
[<c016aaf7>] vfs_readdir+0x77/0x90
[<c016adf0>] filldir64+0x0/0x110
[<c016af6f>] sys_getdents64+0x6f/0xb2
[<c016adf0>] filldir64+0x0/0x110
[<c0102be1>] syscall_call+0x7/0xb
# lsmod
Module Size Used by
I am not using any special modules.
Configuration file attached.
[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 5356 bytes --]
next reply other threads:[~2005-07-09 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 10:20 Justin Piszcz [this message]
2005-07-10 4:20 ` Nathan Scott
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=Pine.LNX.4.63.0507090614290.21767@p34 \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®