Linux LVM users
 help / color / mirror / Atom feed
From: Petro <petro@auctionwatch.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems and questions with LVM on a large raid system.
Date: Thu Mar 13 18:25:02 2003	[thread overview]
Message-ID: <20030314002507.GE22003@auctionwatch.com> (raw)
In-Reply-To: <3E704492.DF386E61@silicide.dk>

On Thu, Mar 13, 2003 at 09:42:58AM +0100, Jon Bendtsen wrote:
> Petro wrote:
> [cut]
> >     The production data we gathered showed the opposite--at least for the
> >     3ware cards in our environment (we had about 5-8% more overhead
> >     running the 3ware cards RAID0 than we did running either raw disk
> >     (cheap IDE cards) or having the 3ware card pretend to be a jbod.
> you mean the cpu was more used ?

    No, meaning we got better overall performance out of Mysql. Fewer
    running threads, threads connected and disconnected better etc. 

  
> >     Unfortunately I'll probably not get a chance to redo these.
> a shame, because if you dont need snapshots, LVM is a overhead.

    It may come to that. 
  
> > > > Since I need the disk write rate of all 6 drives, I'm *REALLY* hoping
> > > > that it's interleaved.
> > > sorry... it is not interleaved.
> > > JonB
> > > ps: how big a partition do you need stripping for? Do you need the
> > > advanced LVM stuff, like resize, snapshot...
> >     I need slightly over 1T of formatted disk space on each system.
> >     Which means i really need to find a way to send an <alt-3> through
> >     an ssh session to a telnet window.
> may i suggest
> http://www.realweasel.com/intro.html
> It's a pci GFX<->serial card.
> I dont have one, but i want 3. If you buy one... do tell us how it
> works.

    That won't solve the problem. 

    See, my servers are 55 miles down the road. I ssh to a machine that
    connects to a private network, on which are a bunch of portmasters
    and APCs. I then telnet to the Portmaster ports, which hook to cua0. 

    It looks basically like I call he "smart hands" at the Colo and talk
    them through redoing the RAID volumes. 

   

-- 
"On two occasions, I have been asked [by members of Parliament], 'Pray, 
Mr. Babbage, if you put into the machine wrong figures, will the right 
answers come out?' I am not able to rightly apprehend the kind of confusion 
of ideas that could provoke such a question." -- Charles Babbage 

  reply	other threads:[~2003-03-13 18:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 13:53 [linux-lvm] Problems and questions with LVM on a large raid system Petro
2003-03-12 16:14 ` jon+lvm
2003-03-12 16:24   ` Kevin P. Fleming
2003-03-12 16:50     ` jon+lvm
2003-03-12 17:00       ` Kevin P. Fleming
2003-03-12 17:17         ` jon+lvm
2003-03-12 17:25           ` Kevin P. Fleming
2003-03-12 17:46   ` Petro
2003-03-13  2:44     ` Jon Bendtsen
2003-03-13 18:25       ` Petro [this message]
2003-03-14  2:32         ` Adrian Phillips
2003-03-15 13:50       ` Steven Lembark
2003-03-15 16:37         ` jon+lvm
2003-03-18  3:14           ` Heinz J . Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2003-03-12 21:03 Barry, Christopher
2003-03-13  2:45 ` Jon Bendtsen

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=20030314002507.GE22003@auctionwatch.com \
    --to=petro@auctionwatch.com \
    --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