From: Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>
To: Oleg Drokin <green@namesys.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
reiser@namesys.com, mfedyk@matchmail.com,
reiserfs-list@namesys.com, copy@harddisk-recovery.nl
Subject: Re: Fwd: Re: Reiser FS performance thingy.
Date: Fri, 8 Aug 2003 12:31:41 +0200 [thread overview]
Message-ID: <20030808123140.A11018@bitwizard.nl> (raw)
In-Reply-To: <20030808100000.GC4607@namesys.com>
On Fri, Aug 08, 2003 at 02:00:00PM +0400, Oleg Drokin wrote:
> Hello!
>
> On Thu, Aug 07, 2003 at 08:58:54PM +0200, Rogier Wolff wrote:
> > > OK Rogier, please search through the archive, and post the URL of your
> > > previous report. That will be most helpful.
> > I searched my own mail archive, remembering that I got an Email
> > from someone named Hans. Do you know him? :-)
>
> I am still interested in a metadata snapshot from the filesystem that
> makes slow block allocations with 2.4.20+ kernels.
> Do you still have one?
Here I go again:
What part of: "We had that problem about a year ago, we were told it
had been fixed. We didn't have the chance to upgrade immediately, but
are now running 2.4.20, which may include the then-proposed fix."
don't you understand.
Hans mailed me about that issue today one year and one day ago. I copied
that Email to the list.
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!
next prev parent reply other threads:[~2003-08-08 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 18:58 Fwd: Re: Reiser FS performance thingy Rogier Wolff
2003-08-08 10:00 ` Oleg Drokin
2003-08-08 10:31 ` Rogier Wolff [this message]
2003-08-08 10:38 ` Oleg Drokin
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=20030808123140.A11018@bitwizard.nl \
--to=r.e.wolff@harddisk-recovery.nl \
--cc=R.E.Wolff@BitWizard.nl \
--cc=copy@harddisk-recovery.nl \
--cc=green@namesys.com \
--cc=mfedyk@matchmail.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.