From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Alex Tomas <alex@clusterfs.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EXT3 extents against 2.6.0-test7
Date: Fri, 17 Oct 2003 15:32:55 -0400 [thread overview]
Message-ID: <3F9043E7.3070606@wmich.edu> (raw)
In-Reply-To: <20031014212359.42243025.alex@clusterfs.com>
kernel BUG at fs/ext3/extents.c:389!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c0198127>] Not tainted
EFLAGS: 00010282
EIP is at ext3_ext_find_extent+0x277/0x570
eax: 00009ac6 ebx: e5257580 ecx: 00000000 edx: e2184940
esi: 00000000 edi: 00000000 ebp: 00000000 esp: ca6adddc
ds: 007b es: 007b ss: 0068
Process find (pid: 10373, threadinfo=ca6ac000 task=ca97b380)
Stack: 00000030 00000050 e7db0200 00458006 00000400 00000000 e2184940
e5257580
00000000 00000000 00000000 00000000 e5257614 e5257614 e5257580
c0199f02
e5257614 00000000 e2184940 e5257580 e5257614 c018fac1 e5257604
00000000
Call Trace:
[<c0199f02>] ext3_ext_get_block+0xb2/0x320
[<c018fac1>] ext3_read_inode+0x221/0x2d0
[<c016b74f>] d_splice_alias+0x4f/0x130
[<c018d57d>] ext3_getblk+0x25d/0x2b0
[<c018d603>] ext3_bread+0x33/0xb0
[<c018a3e1>] ext3_readdir+0x141/0x4e0
[<c0165a7a>] vfs_readdir+0x7a/0x80
[<c0165db0>] filldir64+0x0/0x140
[<c0165f5f>] sys_getdents64+0x6f/0xa9
[<c0165db0>] filldir64+0x0/0x140
[<c01092e7>] syscall_call+0x7/0xb
Code: 0f 0b 85 01 51 fe 2e c0 66 85 c0 0f 84 ee 00 00 00 8b 7c 24
I'm not sure why this is happening. Perhaps due to these ext3 locking
fixes that have been going into the kernel or what?
Upon rebooting my last kernel for the first time in a couple of weeks it
crashed due to fs errors. Now i'm getting this. I only use extents on
a couple non-system partitions, so if i lose anything it's not a huge
deal but I'd like to find out why these errors are suddenly creeping up
so Any other info that's needed just ask and i'll give it.
next prev parent reply other threads:[~2003-10-17 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 18:27 [PATCH] EXT3 extents against 2.6.0-test7 Alex Tomas
2003-10-13 21:39 ` Ed Sweetman
[not found] ` <20031014212359.42243025.alex@clusterfs.com>
2003-10-17 19:32 ` Ed Sweetman [this message]
2003-10-17 20:10 ` Alex Tomas
2003-10-17 20:13 ` Ed Sweetman
2003-10-17 20:41 ` Alex Tomas
2003-10-17 21:22 ` Ed Sweetman
2003-10-17 23:05 ` Alex Tomas
2003-10-18 0:07 ` Ed Sweetman
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=3F9043E7.3070606@wmich.edu \
--to=ed.sweetman@wmich.edu \
--cc=alex@clusterfs.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.