thr3ads.net - Ext3 users - Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0" [Jul 2001]

If this information is useful, please help other people find it:
Share via:

Frédéric L. W. Meunier

2001-Jul-04 10:32 UTC

Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0"

Hi. I was using ext3 0.0.1 without any problems in the last
33 days (same boot). / was still ext2, but I changed /etc/fstab
to ext3. /home/ftp/pub/ is ext3. I mounted
/home/ftp/pub/slakware/bare.i with loopback in /mnt/floppy/.
After some time:

==> /var/log/syslog <=Jul  4 09:40:51 pervalidus kernel: Assertion failure
in
ext3_prepare_write() at inode.c:934: "handle != 0"
Jul  4 09:40:51 pervalidus kernel: Assertion failure in
ext3_prepare_write() at inode.c:934: "handle != 0"
Jul  4 09:40:51 pervalidus kernel: kernel BUG at inode.c:934!
Jul  4 09:40:51 pervalidus kernel: invalid operand: 0000
Jul  4 09:40:51 pervalidus kernel: CPU:    0
Jul  4 09:40:51 pervalidus kernel: EIP:
0010:[ext3_prepare_write+78/336]
Jul  4 09:40:51 pervalidus kernel: EFLAGS: 00010296
Jul  4 09:40:51 pervalidus kernel: eax: 0000001b   ebx:
00000000   ecx: c17a6000   edx: 00000001
Jul  4 09:40:51 pervalidus kernel: esi: c6f81c40   edi:
00000400   ebp: c14eb3fc   esp: cdb31f18
Jul  4 09:40:51 pervalidus kernel: ds: 0018   es: 0018   ss:
0018
Jul  4 09:40:51 pervalidus kernel: Process loop0 (pid: 5470,
stackpage=cdb31000)
Jul  4 09:40:51 pervalidus kernel: Stack: c01eda6c c01edb4d
000003a6 00000400 c14eb3fc 00000400 00000800 da83c2eb 
Jul  4 09:40:51 pervalidus kernel:        d65473c0 c14eb3fc
00000400 00000800 00
Jul  4 09:40:51 pervalidus kernel:        d65473c0 c14eb3fc
00000400 00000800 00000304 d1f79000 c575f4c0 c575f4c0 
Jul  4 09:40:51 pervalidus kernel:        cc7c2000 c0150390
00000286 d1f79104 00000000 00000000 cdb30000 00000000 
Jul  4 09:40:51 pervalidus kernel: Call Trace:
[minix:__insmod_minix_O/lib/modules/2.4.5/kernel/fs/minix/minix.o_+-15637/96]
[ext3_prepare_write+0/336]
[minix:__insmod_minix_O/lib/modules/2.4.5/kernel/fs/minix/minix.o_+-14871/96]
[minix:__insmod_minix_O/lib/modules/2.4.5/kernel/fs/minix/minix.o_+-13465/96]
[kernel_thread+35/48] 
Jul  4 09:40:51 pervalidus kernel: 
Jul  4 09:40:51 pervalidus kernel: Code: 0f 0b 83 c4 0c 90 56
e8 66 15 00 00 89 c7 83 c4 04 8b 53 04

I didn't do anything, just moved to /mnt/floppy/ and
subdirectories. Didn't read or copy any files.

When I tried umount my rxvt freezed and:

root      5471  0.0  0.1  1272  468 ?        D    09:41 0:00 umount /mnt/floppy

No. D ! Is this an ext3 bug, or loopback is still broken in
2.4.5 ? I had no problems mounting without ext3.

WCHAN shows __wait_on_buffer

I just rebooted, after trying without success to use SysRq
and avoid fsck. I'd wait and build 2.4.6, but my load
average...

Any umount -> D.

Parallelizing fsck version 1.22 (22-Jun-2001)
/dev/ide/host0/bus0/target0/lun0/part1 was not cleanly unmounted, check forced.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 97249 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 97304 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 97513 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 194731 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 227190 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 291765 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 875380 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 875386 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 875460 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 1166987 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 1167303 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 1977427 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 2074942 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 2366393 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: Deleted inode 2366430 has zero dtime. 
FIXED.
/dev/ide/host0/bus0/target0/lun0/part1: 33840/2560864 files (4.4%
non-contiguous), 209372/2560351 blocks
/dev/ide/host0/bus0/target0/lun0/part3: clean, 182362/512512 files,
482330/512071 blocks
/dev/ide/host0/bus0/target0/lun0/part4: recovering journal
/dev/ide/host0/bus0/target0/lun0/part4: clean, 7415/645120 files, 168274/644608
blocks

-- 
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-2717-2399 (Niterói-RJ BR)

Stephen C. Tweedie

2001-Jul-04 14:26 UTC

head link

Re: Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0"

Hi,

On Wed, Jul 04, 2001 at 07:32:33AM -0300, Frédéric L. W. Meunier
wrote:> Hi. I was using ext3 0.0.1 without any problems in the last
> 33 days (same boot). / was still ext2, but I changed /etc/fstab
> to ext3. /home/ftp/pub/ is ext3. I mounted
> /home/ftp/pub/slakware/bare.i with loopback in /mnt/floppy/.
> After some time:
> 
> ==> /var/log/syslog <=> Jul  4 09:40:51 pervalidus kernel:
Assertion failure in
> ext3_prepare_write() at inode.c:934: "handle != 0"
> Jul  4 09:40:51 pervalidus kernel: Assertion failure in
> ext3_prepare_write() at inode.c:934: "handle != 0"
That shouldn't be possible in current ext3.  The stable ext3 patches
are now up to version 0.0.8 for 2.4.
>
[minix:__insmod_minix_O/lib/modules/2.4.5/kernel/fs/minix/minix.o_+-15637/96]
> [ext3_prepare_write+0/336]
>
[minix:__insmod_minix_O/lib/modules/2.4.5/kernel/fs/minix/minix.o_+-14871/96]
>
[minix:__insmod_minix_O/lib/modules/2.4.5/kernel/fs/minix/minix.o_+-13465/96]
> [kernel_thread+35/48] 
This doesn't help much --- the modules information looks completely
wrong.  Try running "ksymoops" to do a full decode, rather than
relying on klogd (klogd might be looking at stale module mapping
information).
> When I tried umount my rxvt freezed and:
> 
> root      5471  0.0  0.1  1272  468 ?        D    09:41 0:00 umount
/mnt/floppy
That's probably a side effect of the previous BUG(): a kernel task has
encountered a bug and has frozen.
> No. D ! Is this an ext3 bug, or loopback is still broken in
> 2.4.5 ? I had no problems mounting without ext3.
Loopback should be safe on current ext3.  If you can reproduce this
with ext3-0.0.8, please let me know!

Cheers,
 Stephen

Andrew Morton

2001-Jul-04 14:28 UTC

head link

Re: Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0"

Frédéric L. W. Meunier wrote:> 
> Hi. I was using ext3 0.0.1 without any problems in the last
> 33 days (same boot).
That must be a record of some form!
> / was still ext2, but I changed /etc/fstab
> to ext3. /home/ftp/pub/ is ext3. I mounted
> /home/ftp/pub/slakware/bare.i with loopback in /mnt/floppy/.
> After some time:
yes, loopback was not doing the right thing in 0.0.1.  It'll
fail every time.  0.0.8 works a lot better.

Apparently Analagous Threads

Search for more possibly parallel threads

Ext3 users - Jul 2001 - Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0"

Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0"

Re: Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0"

Re: Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0"

Apparently Analagous Threads