I recently applied the ext3-2.4-0.9.6-249.gz patch to an otherwise
unmodified official-from-Linus 2.4.9 kernel. I built both ext2 and ext3
in as modules, did the "tune2fs -j" incantation, and rebooted.
Mounting / as ext3 worked fine. But a few seconds later, my startup
scripts tried to launch a squad of automounter daemons, and that didn't
work so well. A stream of kernel oopsen follows, all apparently having
something to do with those automount processes. I've attached a copy of
those messages below.
When examining these messages, be aware that I am using autofs4, not
autofs3. That implies a different set of userspace tools as well as an
"autofs4" kernel module. Note, though, that the autofs4 module is a
standard part of the 2.4.9 kernel. Perhaps the ext3 patches create some
sort of conflict with the autofs4 kernel module, heretofore not detected
because most folks are still using autofs3?
It is also worth mentioning that the oopsen appear when using the
ext3-patched kernel even if the no ext3 filesystem is actually being
used. If I change /etc/fstab to request ext2 mounting, the oopsen still
appear. Even if I use tune2fs to actually remove the journal, restoring
the filesystem to pure ext2, the oopsen still appear. I've had no
choice but to revert to a non-ext3-patched kernel. :-(
Any advice would be much appreciated. If there is additional
information you would like to see, you need only tell me how to collect
it and I will oblige.