All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>
To: Hans Reiser <reiser@namesys.com>
Cc: Oleg Drokin <green@namesys.com>,
	reiserfs-list@namesys.com, copy@harddisk-recovery.nl
Subject: Re: ReiserFS problems
Date: Thu, 7 Aug 2003 15:41:08 +0200	[thread overview]
Message-ID: <20030807154107.B7165@bitwizard.nl> (raw)
In-Reply-To: <3F324E06.2080805@namesys.com>

On Thu, Aug 07, 2003 at 05:03:02PM +0400, Hans Reiser wrote:
> Rogier Wolff wrote:
> 
> >>In fact this is not exactly true, it only switches to other "block
> >>group" if you are creating new file. Why do you think this is a
> >>problem?  (of course I am speaking of 2.4.20+ kernels).
> >>   
> >>
> >
> >Well we were recovering data into 1G files, but performance of adding
> >a new block was horrible. It was doing this for every block. Either it
> >was doing a fruitless search on every block-add or it was actually
> >adding the block to another block group. Anyway, performance dropped
> >-=*A LOT*=- when this happened.
> >
> >I think you're describing the way it should be, or "is now", but there
> >was a bug that caused it to behave differently.

> Can you help Oleg investigate this more closely by providing an exact 
> account of what to do to replicate it?  Oleg, replicate this and observe 
> what happens.

What part of: "we reported it a while back, and you told us it was
fixed" don't you understand?

			Roger. 

-- 
+-- Rogier Wolff -- www.harddisk-recovery.nl -- 0800 220 20 20 --
| Files foetsie, bestanden kwijt, alle data weg?!
| Blijf kalm en neem contact op met Harddisk-recovery.nl!

  reply	other threads:[~2003-08-07 13:41 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
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 [this message]
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=20030807154107.B7165@bitwizard.nl \
    --to=r.e.wolff@harddisk-recovery.nl \
    --cc=copy@harddisk-recovery.nl \
    --cc=green@namesys.com \
    --cc=reiser@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.