ext2fs related panic

Stefan Ehmann shoesoft at gmx.net
Sun Nov 7 04:10:45 PST 2004


On Sat, 2004-11-06 at 19:25, Poul-Henning Kamp wrote:
> Ok, can you try the stuff in current, I've made two commits
> and you want both.

Thanks, these fix the previous panics reported by me.

I was able to produce yet another panic:

mount /mnt/stuff
mount -u -o rw /mnt/stuff
touch /mnt/stuff/foo
mount -u -o ro /mnt/stuff
umount /mnt/stuff

At this point I get this:
g_vfs_done():ad1s1[WRITE(offset=4096, length=4096)]error = 1
g_vfs_done():ad1s1[WRITE(offset=8192, length=4096)]error = 1
g_vfs_done():ad1s1[WRITE(offset=20480, length=4096)]error = 1
g_vfs_done():ad1s1[WRITE(offset=27380416512, length=4096)]error = 1

A few seconds later I get this:
Fatal trap 12: page fault while in kernel mode
current process = 55 (syncer)

trace
g_io_request()
bufwrite()
vop_stdfsync()
sched_sync()
fork_exit()
fork_trampoline()

If I do not use mount -u but simply unmount and mount rw afterwards
there seems to be no problem. (So this is not that critcal for me)

> In message <1099751434.868.1.camel at taxman>, Stefan Ehmann writes:
> >On Sat, 2004-11-06 at 14:43, Poul-Henning Kamp wrote:
> >> Ok, then try this patch:
> >Still causing the same panic here.
> >



More information about the freebsd-current mailing list