From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] HUGE LVM log file...
Date: Wed, 18 Jul 2001 21:23:01 +0200 [thread overview]
Message-ID: <20010718212300.E26849@vestdata.no> (raw)
In-Reply-To: <20010718103321.A540@btconnect.com>; from Joe Thornber on Wed, Jul 18, 2001 at 10:33:21AM +0100
On Wed, Jul 18, 2001 at 10:33:21AM +0100, Joe Thornber wrote:
> This comment is interesting:
>
> "Seagate uses horizontal mapping with this drive, so that it reaches
> maximum performance at the beginning of the medium, decreasing at the
> end of the medium."
>
> So obviously this varies from drive to drive.
You can use zcav from the bonnie++ package
(http://www.coker.com.au/bonnie++) to find the transfer-rates for your
drive. I believe finding seek times is a little more tricky since it
depends on where you're seeking from and that will depend on your
application.
--
Ragnar Kjorstad
Big Storage
next prev parent reply other threads:[~2001-07-18 19:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 21:52 [linux-lvm] HUGE LVM log file Gonyou, Austin
2001-07-18 0:00 ` Wolfgang Weisselberg
2001-07-18 8:22 ` Joe Thornber
2001-07-18 8:48 ` Benoit SERRA
2001-07-18 9:33 ` Joe Thornber
2001-07-18 19:23 ` Ragnar Kjørstad [this message]
2001-07-18 22:22 ` lembark
2001-07-18 9:46 ` Adam Cioccarelli
[not found] ` <Pine.LNX.4.33.0107181141480.25686-100000@vie-ac.office.ece tra.com>
2001-07-18 9:47 ` Benoit SERRA
2001-07-18 10:48 ` [linux-lvm] what happens when hdX get hdY in a VG Oliver Jovic
2001-07-18 10:59 ` Joe Thornber
2001-07-18 13:29 ` [linux-lvm] HUGE LVM log file Iain Campbell
2001-07-18 17:02 ` Steven Lembark
-- strict thread matches above, loose matches on Subject: below --
2001-07-17 11:13 Guennadi Liakhovetski
2001-07-17 11:14 ` Heinz J. Mauelshagen
2001-07-17 11:28 ` Guennadi Liakhovetski
2001-07-17 11:28 ` Heinz J. Mauelshagen
2001-07-17 21:28 ` Wolfgang Weisselberg
2001-07-18 14:55 ` Heinz J. Mauelshagen
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=20010718212300.E26849@vestdata.no \
--to=lvm@ragnark.vestdata.no \
--cc=linux-lvm@sistina.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.