From: jose@tridentemonigotes.com
To: green@namesys.com
Cc: reiser <reiserfs-list@namesys.com>
Subject: Re: Desaster Reiser
Date: Fri, 06 Sep 2002 12:06:05 -0400 [thread overview]
Message-ID: <3D78D26D.F24BAAC@tridentemonigotes.com> (raw)
In-Reply-To: 3D78CC6C.C09012AE@tridentemonigotes.com
jose@tridentemonigotes.com wrote:
>
> Oleg Drokin wrote:
> >
> > Hello!
> >
> > On Thu, Sep 05, 2002 at 10:53:35AM -0400, jose@tridentemonigotes.com wrote:
> > > -I have a server 2.4.3 and something HD reiserfs. Yesterday one
> > > of this
> > > HD started to give me problems this is the message.
> >
> > 2.4.3 kernel is very old ad is filled with known bugs both in reiserfs and other
> > parts of code. You should consider upgrading.
> >
> > > After this with reiserfs --check /dev/hdb2 this is the message that gave
> > > me
> >
> > What reiserfsprogs version do you have?
> > If that's not the last one (3.6.3), you should download reiserfsprogs-3.6.3 from
> > our ftp site.
> >
> > > I probed with badblocks and reiserfsck --rebuild -sd but was not
> > > anithing problem and my fear is I wrote that somebody have lose their HD
> > > with reiserfsck --rebuild -tree because after can't mount their units.I
> >
> > That was possible because of reiserfsck crash for example, data are still not
> > lost though partition cannot be mounted.
> >
> > > think that this is the last option if I have another
> > > Have another options before my HD is totally crash and all information
> > > is missing?
> >
> > Well, if you want to be on safe side, you can create metadata snapshot
> > (debugreiserfs -p /dev/device | gzip -9c >metadata.gz) and make it available for
> > us to download.
>
> I attach the file hdb2.gz after I create metadata snapshot. I hope that
> you can verify without any problem
>
> and we can verify that reiserfsprogs will work as expected.
> > Make sure you use reiserfsprogs 3.6.3 version for that operation.
>
> My old version of reiserfsprog was 3.6.2 but now is 3.6.3
>
> > Or you can download reiserfsprogs 3.6.3 and run reiserfsck --rebuild-tree
> > from there and only contact us if it will crash. (with metaadta, too).
>
> Respect this I would like another options before if that posible
> >
> > Also after your problems are over you will need to upgrade the kernel to avoid
> > future corruptions.
>
> You sure that after this problem I will upgrading and check the units
> every week
> >
> >Thank You
> By
>
> Jose
prev parent reply other threads:[~2002-09-06 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 14:53 Desaster Reiser jose
2002-09-05 10:09 ` Oleg Drokin
2002-09-05 11:04 ` Hans Reiser
2002-09-05 16:32 ` Rafael E. Herrera
2002-09-05 20:02 ` Hans Reiser
[not found] ` <3D78CC6C.C09012AE@tridentemonigotes.com>
2002-09-06 16:06 ` jose [this message]
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=3D78D26D.F24BAAC@tridentemonigotes.com \
--to=jose@tridentemonigotes.com \
--cc=green@namesys.com \
--cc=reiserfs-list@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.