Hi,
Sorry, I forgot to say, that it was with 0.0.2b. Also I reproduced
this twice, so the second time, it _was_ a clean fs before converting
to ext3.
Miklos
> > 5) boot, then mount ext3 filesystem - it says:
> > JFS DEBUG: (recovery.c, 411): journal_recover: JFS: recovery, exit status 0,
>recovered transactions 130 to 133
> > 6) unmount the fs, and with debugfs turn off journalling
> > 7) "e2fsck -f" the filesystem
>
> > And fsck returned some errors. Is this normal?
>
> Which version of ext3? If you haven't applied the 0.0.2a and 0.0.2b
> patches, then yes, there have been bugs fixed which might have caused
> this. Another possible danger is applying a journal to a filesystem
> which is not completely clean and which has undetected errors ---
> eventually the user mode tools for journal creation will be advanced
> enough not to allow creation of a journal on an unclean filesystem.
