EXT3 'kernel BUG' in 0.05e?

Matija Nalis
Mon, 05 Feb 2001 17:48:34 -0000

After approx. two weeks of uptime. This host always has some network
activity, and when it happened, it was either running or had just finished
making backup of about 1200MB (from few ext3 to one ext3 filesystem).

kernel was still alive to network pings and services responded, but trying
to ssh failed (just hanged there before opening session but after giving
last login info). telneting to pop3 port worked, but upon authenticating it
also hang - so I'm assuming VFS or specific ext3 filesystem is hanging.

kernel is 2.2.19pre7 (with openwall patches, although it should not matter),
ext3 is 0.05e.
All filesystems are ext3 (in journal data mode).
Machine is PIII/600 with 128MB RAM, 300MB swap.
Journals are 5-15MB in size. Partitions are 150MB to 7,5GB.

After approx. two weeks of uptime. This host always has some network
activity, and when it happened, it was either running or had just finished
making backup of about 1200MB (from few ext3 to one ext3 filesystem).

kernel was still alive to network pings and services responded, but trying
to ssh failed (just hanged there before opening session but after giving
last login info). telneting to pop3 port worked, but upon authenticating it
also hang - so I'm assuming VFS or specific ext3 filesystem is hanging.

kernel is 2.2.19pre7 (with openwall patches, although it should not matter),
ext3 is 0.05e.
All filesystems are ext3 (in journal data mode).
Machine is PIII/600 with 128MB RAM, 300MB swap.
Journals are 5-15MB in size. Partitions are 150MB to 7,5GB.

Feb  5 12:28:28 blue kernel: Buffer locked in journal_write_metadata_buffer,
flags 0x00004a0f, count 1
Feb  5 12:28:28 blue kernel: kernel BUG at journal.c:306!
Feb  5 12:28:28 blue kernel: invalid operand: 0000
Feb  5 12:28:28 blue kernel: CPU:    0
Feb  5 12:28:28 blue kernel: EIP:    0010:[journal_write_metadata_buffer+71/440]
Feb  5 12:28:28 blue kernel: EFLAGS: 00010286
Feb  5 12:28:28 blue kernel: eax: 0000001d   ebx: 00000000   ecx: c0236028
edx: c407c000
Feb  5 12:28:28 blue kernel: esi: c0d8da60   edi: c0d8da60   ebp: 00000000
esp: c1bb3e68
Feb  5 12:28:28 blue kernel: ds: 0018   es: 0018   ss: 0018
Feb  5 12:28:28 blue kernel: Process kjournald (pid: 76, process nr: 10,
stackpage=c1bb3000)
Feb  5 12:28:28 blue kernel: Stack: 00000132 c1bb3fc4 c0d8da60 c7f8b380 c1bb3fc8
00000000 c015a614 c4a7b480
Feb  5 12:28:28 blue kernel:        c0d8da60 c1bb3fc4 00000afb c170d400 c170d080
c170d500 c170d580 c170d600
Feb  5 12:28:28 blue kernel:        c170d480 c170d700 c170d780 c6713480 c6713300
c6713580 c6713600 c6713680
Feb  5 12:28:28 blue kernel: Call Trace: [journal_commit_transaction+1628/4212]
[schedule+477/932] [kjournald+307/472] [commit_timeout+0/12]
[kernel_thread+35/48]
Feb  5 12:28:28 blue kernel: Code: 0f 0b 83 c4 0c 8b 7c 24 1c 8b 47 18 a8 02 75
29 68 62 9b 20

Any ideas ?

--
Opinions above are GNU-copylefted.