All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelsha@ez-darmstadt.telekom.de>
To: Martyn.AYSHFORD@orange.co.uk
Cc: linux-lvm@msede.com, mge@u9ete.ez-darmstadt.telekom.de
Subject: Re: [linux-lvm] Swap/DB devices
Date: Thu, 15 Apr 1999 16:24:10 METDST	[thread overview]
Message-ID: <199904151425.AA22497@mailgate1b.telekom.de> (raw)
In-Reply-To: <199904150815.AA02380@future-is.orange.co.uk>; from "Martyn.AYSHFORD@orange.co.uk" at Apr 15, 99 9:18 am

> 
> I'm in the process of re-jigging all the file systems to sit in volume
> groups.
> 
> Two questions :-
> 
> a) Can I setup swap to run from a volume group is it a good idea?

Yes.
It's as good as partition based swap (very low LVM driver overhead).

Please take i/o amounts into consideration and avoid to allocate swap LVs
and other i/o intensive LVs on the same PVs.

> 
> b) I have  database devices running in cooked file systems for Oracle,
> Sybase and Informix.
> 
> Vendor recommendations for sybase and Informix are normally raw, here we
> carve our database devices from HP volume groups is this a good idea for
> linux?

There is a raw device patch available by Stephen Tweedie.
IIRC it will make it into the 2.3 kernel (what do you say Stephen?).

LVM has to be enhanced a little bit to support that patch.

> 
> Anybody done this?
> 

Yes, i did successfull tests with a lot of swap LVs.
Anybody out there with (big) database installations on LVM?

BTW: you can have performance boosts by setting up striped LVs
     if your hardware setup is o.k. (enough i/o bandwith on scsi busses,
     several busses ...)
     


Regards,
Heinz

--

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Systemmanagement C/S                             Deutsche Telekom AG
                                                 Entwicklungszentrum Darmstadt
Heinz Mauelshagen                                Otto-Roehm-Strasse 71c
Senior Systems Engineer                          Postfach 10 05 41
                                                 64205 Darmstadt
mge@ez-darmstadt.telekom.de                      Germany
                                                 +49 6151 886-425
                                                          FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  parent reply	other threads:[~1999-04-15 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-15  8:18 [linux-lvm] Swap/DB devices Martyn.AYSHFORD
1999-04-15 14:10 ` Stephen C. Tweedie
1999-04-15 14:24 ` Heinz Mauelshagen [this message]
1999-04-16 20:43   ` Stephen C. Tweedie
1999-04-16 21:47     ` Heinz Mauelshagen
1999-04-17  0:14       ` Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
1999-04-17 11:22 [linux-lvm] Swap/DB devices (fwd) Heinz Mauelshagen
1999-04-17 20:03 ` [linux-lvm] Swap/DB devices Stephen C. Tweedie
1999-04-20 22:34 Heinz 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=199904151425.AA22497@mailgate1b.telekom.de \
    --to=mauelsha@ez-darmstadt.telekom.de \
    --cc=Martyn.AYSHFORD@orange.co.uk \
    --cc=linux-lvm@msede.com \
    --cc=mge@u9ete.ez-darmstadt.telekom.de \
    /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.