> > For recovering broken machine, I'd like to mount without replaying journal.
>
> You cannot mount without replaying even in read-only mode, because
> file-system meta-data are possibly inconsistent.
Then suse's use of reiserfs is pretty b0rken. Putting reiserfsck on /
partition is pretty useless -- if it crashes during mount you can't
repair it.
If reiserfsck detects errors on /, you can't repair them because
reiserfsck is on that partition. Ouch.
> > [reiserfs panics while replaying journal; seems there are still some bugs
> > hidden in there]. Unfortunately, "nolog" option does not seem imlemented.
>
> There is a patch allowing to mount reiserfs if there was io error during
> journal replay on mount. It is included into 2.4.9-ac* tree (it was sent
> to Linus several times, but this did not avail).
I already repaired my system -- had to install another copy of suse to
another partition :-(.
> Can you send to Reiserfs mail-list <Reiserfs-List@Namesys.COM> more
> detailed information about your case, like ksymoopsed stack trace,
> etc.
No stack trace, sorry. It refused to mount saying that attempting to
write into log block.. That's panic. Reiserfsck is not usable in such
case, because ... how do you run reiserfsck from partition you can't
mount?
Pavel
-- The best software in life is free (not shareware)! Pavel GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/