Bug 23648 - ext3_new_block Oops
ext3_new_block Oops
Status: CLOSED CURRENTRELEASE
Product: Red Hat High Availability Server
Classification: Retired
Component: ext3 (Show other bugs)
beta
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Stephen Tweedie
Wil Harris
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-09 04:35 EST by Need Real Name
Modified: 2007-04-18 12:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-01-09 05:58:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Invalidate-buffers patch (318 bytes, patch)
2001-01-09 05:58 EST, Stephen Tweedie
no flags Details | Diff

  None (edit)
Description Need Real Name 2001-01-09 04:35:48 EST
I got Oops when using ext3-0.05d:

enviroment and configure:
official 2.2.18 kernel, with only kdb patch and ext3 patch contains
in ext3-0.05d package, no reject or fuzz. compile ext3 direct 
into the kernel.

Make a clean 200M ext2 partition and mount it, produce a 10M
journal file, then remount it as ext3. Every operations is ok.
Then umount it, repeat the same action( mke2fs, produce journal
file, remount), and copy a large directory with many files to
this partition, Oops occured:

Eric kernel: Assertion failure in ext3_new_block() at balloc.c line 709:
"!test_
and_set_bit(BH_Alloced, &bh->b_state)"

Oops: 0002
CPU:    0
EIP:    0010:[<c0148d60>]
EFLAGS: 00010246
eax: 0000006d   ebx: 00000400   ecx: 0000004a   edx: 0000002d
esi: c7f8d000   edi: ffffffff   ebp: c49d1dd4   esp: c49d1d70
ds: 0018   es: 0018   ss: 0018
Process cp (pid: 689, process nr: 27, stackpage=c49d1000)
Stack: c01c877f 000002c5 c01c89a0 c3183a90 00000005 c3183a90 c3602f20
c3602f20
       c0ccaca0 c3898020 c012bdd7 00000309 c37a9800 c36df800 00000000
c49d1dd0
       00000112 c7f85000 c31da880 00000112 c3602f20 00000112 00000004
c31d5040
Call Trace: [<c01c877f>] [<c01c89a0>] [<c012bdd7>] [<c014b4e7>]
[<c014ba6f>] [<c
014be06>] [<c0149a43>]
       [<c0121464>] [<c0121464>] [<c0121459>] [<c0121525>] [<c0121464>]
[<c012a3
a4>] [<c0149720>] [<c010a24c>]
Code: c6 05 00 00 00 00 00 83 c4 14 89 f6 8b 45 cc f0 0f ba 70 18
Comment 1 Stephen Tweedie 2001-01-09 05:53:10 EST
OK, looks as if some of the debugging flags are being carried over between
mounts.  I'll look into this.  Is this repeatable?
Comment 2 Stephen Tweedie 2001-01-09 05:58:29 EST
Created attachment 7284 [details]
Invalidate-buffers patch
Comment 3 Stephen Tweedie 2001-01-09 05:59:59 EST
Should be fixed by the attached patch, which I'll include in the next release.

Note You need to log in before you can comment on or make changes to this bug.