ext2fs related panic

Stefan Ehmann shoesoft at gmx.net
Sun Nov 7 04:35:38 PST 2004


On Sun, 2004-11-07 at 13:16, Poul-Henning Kamp wrote:
> In message <1099829438.890.11.camel at taxman>, Stefan Ehmann writes:
> >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)
> 
> this is a long-standing bug in ext2fs which were previously masked
> by other issues:  When downgrading a filesystem from r/w to r/o
> the dirty buffers are not flushed.

For a long time remounting it rw didn't work at all for ext2fs. Recently
it seemed to start working for me (I use it very rarely though).

But as stated above, this is a bug I can live with as it can be easily
be workaround by completely unmounting the fs.

Thanks again for the quick fixes.



More information about the freebsd-current mailing list