From: Chris Mason <mason@suse.com>
To: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: Working reiserfsck?
Date: Tue, 07 Aug 2001 11:26:50 -0400 [thread overview]
Message-ID: <146010000.997198010@tiny> (raw)
In-Reply-To: <20010802133051.A88@toy.ucw.cz>
On Thursday, August 02, 2001 01:30:55 PM +0000 Pavel Machek <pavel@ucw.cz>
wrote:
> Hi!
>
> On one of my machines, I installed reiserfs on / fs.... and got to habit
> of just powering that machine down with powerswitch. I was running
> various kernels at least from 2.4.3 on it.
>
> Now I tried to run reiserfsck, and (besides it having very ugly UI) it
> reported some problems. Question is, how to correct those? reiserfsck
> attitude seems to be "run me and I'll kill your filesystem". Is it really
> that dangerous? Where to get working reiserfsck?
> Pavel
The best reiserfsck version right now is in
ftp.namesys.com/pub/reiserfsprogs/pre
It should fix the problem, backups are always handy though.
-chris
next prev parent reply other threads:[~2001-08-07 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 13:30 Working reiserfsck? Pavel Machek
2001-08-07 15:26 ` Chris Mason [this message]
2001-08-08 0:55 ` Aaron Smith
2001-08-09 16:15 ` Pavel Machek
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=146010000.997198010@tiny \
--to=mason@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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