From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Reiserfs: how to mount without journal replay?
Date: Thu, 30 Aug 2001 15:04:44 -0700 [thread overview]
Message-ID: <20010830150444.C1451@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20010826130858.A39@toy.ucw.cz> <15246.11218.125243.775849@gargle.gargle.HOWL> <20010830225323.A18630@atrey.karlin.mff.cuni.cz> <3B8EAD35.5695B30B@namesys.com> <20010830235005.B9330@bug.ucw.cz>
In-Reply-To: <20010830235005.B9330@bug.ucw.cz>
On Thu, Aug 30, 2001 at 11:50:05PM +0200, Pavel Machek wrote:
> Hi!
>
> > > 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.
>
> ext2 is willing to mount ro even with known inconsistencies. SuSE 7.1
> does not come with 'live filesystem' and install cd does not have
> reiserfsck on it. Too bad. You have to install somewhere to be able to
> run reiserfsck on suse7.1.
Hmm. Is there any chance of *not* replaying the log on mount-ro, and using
a combination of on disk meta-data, and journal?
next prev parent reply other threads:[~2001-08-30 22:04 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
2001-08-30 21:50 ` Pavel Machek
2001-08-30 22:04 ` Mike Fedyk [this message]
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=20010830150444.C1451@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
/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