Bug#419175: I agree, this needs a kernel code fix

[Dominique Brazziel <dbrazziel@snet.net>]

The journal gets fouled up after the partition is
remounted read-only and even after unmount/fsck, upon
remount the error flag remains and a message is issued
that the partition needs to be fsck'ed.  Only way to
proceed was to delete and remake the journal with
tunefs2. 

I've put both the hacks into /etc/rc.local and have my
fingers crossed but it would be nice (and right) to
have some restart code in the kernel.

That code posted above looks interesting, maybe I'll
see if I can adapt it to my system and give it a
whirl...