All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>
Cc: reiserfs-list@namesys.com, copy@harddisk-recovery.nl,
	Jeff Mahoney <jeffm@suse.com>
Subject: Re: ReiserFS problems
Date: Wed, 06 Aug 2003 20:43:38 +0400	[thread overview]
Message-ID: <3F31303A.6020408@namesys.com> (raw)
In-Reply-To: <20030806182055.A28562@bitwizard.nl>

Vitaly, when --rebuild-tree is used, warn the user "rebuilding tree, 
once this is started it must be finished or the filesystem will be 
unusable.  If you kill it or the machine crashes before it finishes, run 
it again.".

Also explain this in the doc for --rebuiild-tree.

Hans

>
>
>Question: If it is reading all datablocks, I'm guessing that it is
>looking for the magics that build up the filesystem.
>
not sure what a magic is.  Perhaps you mean formatted nodes.

> We're a
>datarecovery company. We probably don't have any current
>datarecoveries of people with Reiserfs on their disk. But if we had a
>disk-image with a valid (or not) Reiserfs on it, would it link that
>into our filesytem? to 
>
If you store a copy of reiserfs on reiserfs, it totally screws fsck for 
V3.  V4 has some features added to the node format specifically to avoid 
that.

>
>We've noticed horrible slowdowns when the filesystem is > 90% full. It
>turns out that when a block group is more than 90% full reiserfs will
>prefer a different block group. i.e. it is ALWAYS switching block
>groups when the whole disk is > 90% full. Something like that. When we
>report something like that it's always: Ah, yes, that's an old bug
>we've fixed it. Use patch.....
>
I don't think you reported that to me.....

Jeff, give me an opinion on this....

For V4 we have a repacker.

-- 
Hans



  reply	other threads:[~2003-08-06 16:43 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 16:20 ReiserFS problems Rogier Wolff
2003-08-06 16:43 ` Hans Reiser [this message]
2003-08-06 18:41   ` Jeff Mahoney
2003-08-06 19:21     ` Rogier Wolff
2003-08-06 19:36       ` Rogier Wolff
2003-08-06 22:08         ` Mike Fedyk
2003-08-07  4:40           ` Rogier Wolff
2003-08-06 19:40       ` Vitaly Fertman
2003-08-07 15:05     ` Hans Reiser
2003-08-07 15:53       ` Jeff Mahoney
2003-08-08 13:07         ` Hans Reiser
2003-08-06 20:48   ` Bernd Schubert
2003-08-06 16:48 ` Oleg Drokin
2003-08-06 17:18   ` Rogier Wolff
2003-08-06 17:28     ` Oleg Drokin
2003-08-06 17:49       ` Rogier Wolff
2003-08-06 18:10         ` Vitaly Fertman
2003-08-07 13:22       ` Hans Reiser
2003-08-07 18:12         ` Mike Fedyk
2003-08-08  0:18           ` Russell Coker
2003-08-08 11:29             ` [OT] " Christian Kujau
2003-08-08 12:40               ` Nikita Danilov
2003-08-08 13:06                 ` Carl-Daniel Hailfinger
2003-08-08 12:59               ` Russell Coker
2003-08-08 15:39                 ` Christian Kujau
2003-08-09  0:45                 ` The Amazing Dragon
2003-08-08  9:56           ` Oleg Drokin
2003-08-06 17:43     ` Andreas Dilger
2003-08-06 17:52       ` Rogier Wolff
2003-08-07 13:27         ` Hans Reiser
2003-08-07 13:03     ` Hans Reiser
2003-08-07 13:41       ` Rogier Wolff
2003-08-07 18:44         ` Mike Fedyk
2003-08-06 17:22   ` Rogier Wolff
2003-08-06 18:01     ` Vitaly Fertman
2003-08-06 18:14       ` Rogier Wolff
2003-08-06 18:22         ` Rogier Wolff
2003-08-06 19:03           ` Oleg Drokin
2003-08-06 19:04           ` Vitaly Fertman
2003-08-07 13:35           ` Hans Reiser
2003-08-07 13:46             ` Rogier Wolff
2003-08-07 14:11               ` Vitaly Fertman
2003-08-06 18:52         ` Vitaly Fertman
2003-08-07 12:58   ` Hans Reiser
2003-08-07 13:24     ` Russell Coker
2003-08-07 14:41       ` Hans Reiser
2003-08-06 16:52 ` Andreas Dilger

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=3F31303A.6020408@namesys.com \
    --to=reiser@namesys.com \
    --cc=R.E.Wolff@harddisk-recovery.nl \
    --cc=copy@harddisk-recovery.nl \
    --cc=jeffm@suse.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.