From: Andreas Dilger <adilger@turbolabs.com>
To: ReiserFS Mailingliste <reiserfs-list@namesys.com>,
LVM List <linux-lvm@sistina.com>
Subject: [linux-lvm] Re: [reiserfs-list] Horrid performance with 2.4.{9,10,12} + LVM + ReiserFS
Date: Wed, 17 Oct 2001 16:30:56 -0600 [thread overview]
Message-ID: <20011017163056.A508@turbolinux.com> (raw)
In-Reply-To: <20011018000006.A22777@jensbenecke.de>
On Oct 18, 2001 00:00 +0200, Jens Benecke wrote:
> The LVM volume is about 97% full (7.5GB free). In ext2 the rule was not to
> use the last 5% of a disk because it would be too slow. But I think this
> should not be a problem for ReiserFS, at least not with such big disks (?).
> If it is, this would waste over 10GB disk space which I don't think is
> acceptable.
Do you mean that you have 3% of the LOGICAL VOLUME or DISK free, or do you
have 3% of the FILESYSTEM free (e.g. is the free space reported by "pvscan"
or "df")? If it is the FILESYSTEM with only 3% free, then there is not much
that you can do about the performance problem - fragmentation cannot be
helped, regardless of the filesystem.
Actually, there is someone testing exactly this issue with reiserfs, and they
report 5-10x slowdown with a highly fragmented filesystem, so your 2.5x
slowdown is in the right range.
> Strangely, on a 'real' partition this is much faster (this was formatted
> recently and with 3.6 format, though):
Yes, well a new filesystem (especially if not full) will not have
fragmentation problems.
> Currently I'm thinking of backing up the whole volume and reformatting, but
> I wanted to ask what might cause this first because this would be a major
> PITA for many users here.
Well, it may help for a short time, but at 97% full you will have problems
almost right away again. I'd suggest adding more space to the LV and growing
the filesystem (without doing the backup/restore) and you will naturally get
some "defragmentation" happening as the new space is used and old space is
freed.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next parent reply other threads:[~2001-10-17 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011018000006.A22777@jensbenecke.de>
2001-10-17 22:30 ` Andreas Dilger [this message]
2001-10-17 23:00 ` [linux-lvm] Re: [reiserfs-list] Horrid performance with 2.4.{9,10,12} + LVM + ReiserFS Hans Reiser
2001-10-18 0:48 ` [linux-lvm] " José Luis Domingo López
2001-10-18 9:17 ` Werner John
[not found] ` <20011019030045.O25054@jensbenecke.de>
2001-10-19 1:19 ` Eric M. Hopper
2001-10-19 5:49 ` Werner John
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=20011017163056.A508@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=linux-lvm@sistina.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.