All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Hans Reiser <reiser@namesys.com>,
	Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>,
	reiserfs-list@namesys.com, copy@harddisk-recovery.nl
Subject: Re: ReiserFS problems
Date: Wed, 6 Aug 2003 21:21:07 +0200	[thread overview]
Message-ID: <20030806212107.A3975@bitwizard.nl> (raw)
In-Reply-To: <3F314BE8.50300@suse.com>

On Wed, Aug 06, 2003 at 02:41:44PM -0400, Jeff Mahoney wrote:
> What is the workload that is producing the horrible slowdowns?

write at 20Mb per second into files of 1Gb each. 

It was reported, and you guys told me it was a bug that had 
been fixed.  we refused to upgrade to the recommended version
back then. But we might have gotten an upgrade due to a general
kernel upgrade since then. But we try to keep the filesystem
at < 90% full anyway. 

Recommendation: Make that "10%" a variable, settable by the
"reserved-for-root" parameter...

Is there a way that allows me to see the fill-percentage of
our block groups?

	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-06 19:21 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 [this message]
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=20030806212107.A3975@bitwizard.nl \
    --to=r.e.wolff@harddisk-recovery.nl \
    --cc=copy@harddisk-recovery.nl \
    --cc=jeffm@suse.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.