From: Bradley M Alexander <storm@tux.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM performance
Date: Thu Nov 22 23:24:02 2001 [thread overview]
Message-ID: <20011123002611.N5393@sonsofthunder.yi.org> (raw)
In-Reply-To: <NBBBKLKHMJHIJLHOGAOJIEACJCAA.steve.wray@the.net.nz>
On Fri, Nov 23, 2001 at 05:32:07PM +1300, Steve Wray wrote:
>
> thats dead right; ide can't simultaneously write to the master and slave
> on the same controller. Also, the pair of drives uses the controller
> circuitry
> of the master, so it always pays to make the master the most modern one.
Since both controllers have a drive master and a cd slave, this shouldn't
matter, per se.
>
> > Can anyone give me any ideas as to why the machine gets beaten about so
> > much during IO operations and more importantly how can I minimize the
> > impact.
>
> Dunno, if it was because the fs is striped across those drives then
> splitting them across controllers would have made it go away.
Nothing should be striped across the drives. I have two PVs and made two
VGs, one on each drive. The way it works out, the data I am mastering is on
vg01 (hdc), and the ISO is being created there as well. the CD write actually
happens from hdc -> hdd.
> I've seen no performance problems at all and really thrashed an LVM-root
> machine for test purposes while working on a movie. It took it well,
> performance-wise. (reliability is another issue; never go LVM-root...
> but thats just my 2 cents, YMMV).
Yeah, I wasn't brave enough to go all out...And with the problems I was
having, I'm glad I made that decision. :)
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
--Brad
============================================================================
Bradley M. Alexander, CISSP | Co-Chairman,
Beowulf System Admin/Security Specialist | NoVALUG/DCLUG Security SIG
Debian/GNU Linux Developer | storm@debian.org
| storm@tux.org
============================================================================
You start with a bag full of luck and an empty bag of
experience. The trick is to fill the bag of experience before you
empty the bag of luck.
--Rules of the Air, #16
next prev parent reply other threads:[~2001-11-22 23:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 22:15 [linux-lvm] LVM performance Bradley M Alexander
2001-11-22 22:31 ` Steve Wray
2001-11-22 23:24 ` Bradley M Alexander [this message]
2001-11-23 6:33 ` Steve Wray
2001-11-23 9:11 ` Steven Lembark
2001-11-23 8:08 ` Benjamin Scott
2001-11-25 21:15 ` Steven Lembark
2001-11-27 12:24 ` Duncan Young
[not found] <3BFDEE1A.1161DD24@dpma.de>
2001-11-23 8:11 ` Benjamin Scott
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 17:34 Alan Willis
2002-11-09 3:05 ` Joe Thornber
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=20011123002611.N5393@sonsofthunder.yi.org \
--to=storm@tux.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox