public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Nikita Danilov <Nikita@namesys.com>, Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org, research@suse.de
Subject: Re: Reiserfs: how to mount without journal replay?
Date: Fri, 31 Aug 2001 01:16:37 +0400	[thread overview]
Message-ID: <3B8EAD35.5695B30B@namesys.com> (raw)
In-Reply-To: <20010826130858.A39@toy.ucw.cz> <15246.11218.125243.775849@gargle.gargle.HOWL> <20010830225323.A18630@atrey.karlin.mff.cuni.cz>

Pavel Machek wrote:
> 
> 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.

Every filesystem has this problem, if the root directory gets hosed you have to
use the CDROM.
Booting from CDROM with SuSE is not such a problem.

> 
> 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 :-(.


I boot from CDROM when I have such problems.

> 
> > 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/

  reply	other threads:[~2001-08-30 21:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-26 13:08 Reiserfs: how to mount without journal replay? Pavel Machek
2001-08-30 12:04 ` Nikita Danilov
2001-08-30 20:53   ` Pavel Machek
2001-08-30 21:16     ` Hans Reiser [this message]
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=3B8EAD35.5695B30B@namesys.com \
    --to=reiser@namesys.com \
    --cc=Nikita@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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