[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

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





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]