All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Philippe Gramoull? <philippe.gramoulle@mmania.com>
Cc: reiserfs <reiserfs-list@namesys.com>
Subject: Re: corrupted 3.5 format fs
Date: Thu, 22 Aug 2002 09:43:56 +0400	[thread overview]
Message-ID: <20020822094356.A1660@namesys.com> (raw)
In-Reply-To: <20020822063512.54daaeaf.philippe.gramoulle@mmania.com>

Hello!

On Thu, Aug 22, 2002 at 06:35:12AM +0200, Philippe Gramoull? wrote:

> So , i did and re-ran --check and came with still 1 corruption left that was
> said to be able to be corrected with --fix-fixable.
> Re-ran --fix-fixable and --check , and i still had this '1 corruption found
> which can be fixed with --fix-fixable'
> bad_stat_data: block 38372, [3955 5371 0x0 SD (0)], SD has bad nlink number

SOmetimes it is hard to tell whenever corruption that looks like it can be fixed
at --fix-fixable will be fixed at this stage or not.
Of course it is a bug taht fix-fixable does not recommend to use
--rebuild-tere.
Currently this is a rule of thumb that if you get corruptions after
--fix-fixable stage, you should run --rebuild-tree.

> http://philippemm.multimania.com/reiserfs/3.5_var_corrupted_fs.txt
> and the gzipped metadata here;
> http://philippemm.multimania.com/reiserfs/metadata.gz

Got it, thank you.

Bye,
    Oleg

  reply	other threads:[~2002-08-22  5:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-22  4:35 corrupted 3.5 format fs Philippe Gramoullé
2002-08-22  5:43 ` Oleg Drokin [this message]
2002-08-22 11:55   ` Vitaly Fertman
2002-08-22 12:29     ` 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=20020822094356.A1660@namesys.com \
    --to=green@namesys.com \
    --cc=philippe.gramoulle@mmania.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.