From: Vitaly Fertman <vitaly@namesys.com>
To: Bill Schrier <wschrier@neolinear.com>, Oleg Drokin <green@namesys.com>
Cc: it@neolinear.com, reiserfs-list@namesys.com
Subject: Re: reiserfsck failure
Date: Thu, 16 Jan 2003 16:48:51 +0300 [thread overview]
Message-ID: <200301161648.51232.vitaly@namesys.com> (raw)
In-Reply-To: <3E26B146.E09BCF45@neolinear.com>
Hi,
On Thursday 16 January 2003 16:19, Bill Schrier wrote:
> Oleg, creating that file now. I will send instructions on where/how to
> download once it is ready.
>
> Vitaly, I'm sure that I used the same reiserfsck each time. We did nothing
> on the system to change anything. It is possible that the core file came
> from the --check run. Over the past week or so, we've run one --check, one
> --rebuild-tree that failed, and one --rebuild-tree that succeeded. The
> system is now up and running in a usable state.
>
> Bill
If your system is now recovered then that metadata dump you are making with
debugreiserfs won't be very useful - it can just show the state of files you
have now, but not before, when fsck segfaults. Please use the uptodate version
of reiserfsprogs, for now it is 3.6.4. And do not forget to email us with any
problem you have.
--
Thanks,
Vitaly Fertman
next prev parent reply other threads:[~2003-01-16 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E247A12.4E479B64@neolinear.com>
2003-01-14 21:01 ` reiserfsck failure Bill Schrier
2003-01-15 6:59 ` Oleg Drokin
2003-01-15 20:15 ` Bill Schrier
2003-01-16 9:32 ` Oleg Drokin
2003-01-16 13:19 ` Bill Schrier
2003-01-16 13:48 ` Vitaly Fertman [this message]
2003-01-16 13:50 ` Vitaly Fertman
2004-02-24 14:24 Vance_Petree
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=200301161648.51232.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=green@namesys.com \
--cc=it@neolinear.com \
--cc=reiserfs-list@namesys.com \
--cc=wschrier@neolinear.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.