From: Bill Schrier <wschrier@neolinear.com>
To: Oleg Drokin <green@namesys.com>
Cc: it@neolinear.com, reiserfs-list@namesys.com, vitaly@namesys.com
Subject: Re: reiserfsck failure
Date: Thu, 16 Jan 2003 08:19:02 -0500 [thread overview]
Message-ID: <3E26B146.E09BCF45@neolinear.com> (raw)
In-Reply-To: 20030116123255.A16554@namesys.com
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
Oleg Drokin wrote:
> Hello!
>
> On Wed, Jan 15, 2003 at 03:15:13PM -0500, Bill Schrier wrote:
> > Unfortunatly, the console was completely hosed up and I couldn't even get any
> > display on it to record any messages to stderr. Sorry - don't think I can help
> > there...
>
> Hm. You still have not told us what version of reiserfsck was that.
> Also can you please capture metadata snapshot for us
> (debugreiserfs -p /dev/yourdevice | bzip2 -9c >metadata.bz2 )
> and make it available for us to download?
> Thank you.
>
> Bye,
> Oleg
--
William J. Schrier Phone: 412.968.5780 x151
Neolinear, Inc. Fax: 412.968.5788
583 Epsilon Drive Email: wschrier@neolinear.com
Pittsburgh, PA 15238
next prev parent reply other threads:[~2003-01-16 13:19 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 [this message]
2003-01-16 13:48 ` Vitaly Fertman
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=3E26B146.E09BCF45@neolinear.com \
--to=wschrier@neolinear.com \
--cc=green@namesys.com \
--cc=it@neolinear.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@namesys.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.