From: Pavel Machek <pavel@suse.cz>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, research@suse.de
Subject: Re: Reiserfs: how to mount without journal replay?
Date: Thu, 30 Aug 2001 22:53:23 +0200 [thread overview]
Message-ID: <20010830225323.A18630@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20010826130858.A39@toy.ucw.cz> <15246.11218.125243.775849@gargle.gargle.HOWL>
In-Reply-To: <15246.11218.125243.775849@gargle.gargle.HOWL>; from Nikita@Namesys.COM on Thu, Aug 30, 2001 at 04:04:34PM +0400
Hi!
> > 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+
next prev parent reply other threads:[~2001-08-30 20:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-26 13:08 Pavel Machek
2001-08-30 12:04 ` Nikita Danilov
2001-08-30 20:53 ` Pavel Machek [this message]
2001-08-30 21:16 ` Hans Reiser
2001-08-30 21:50 ` Pavel Machek
2001-08-30 22:04 ` Mike Fedyk
2001-08-30 22:10 ` Dan Hollis
2001-08-30 22:15 ` Rafael Herrera
2001-08-30 22:32 ` Alan Cox
2001-09-04 20:53 ` Chris Mason
2001-09-04 21:33 ` Hans Reiser
2001-09-05 2:01 ` Chris Mason
2001-08-30 21:30 ` Mike Fedyk
2001-08-30 21:35 ` Hans Reiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010830225323.A18630@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--cc=Nikita@Namesys.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=research@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®