Linux LVM users
 help / color / mirror / Atom feed
From: "Christian Limpach" <chris@Pin.LU>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] offtopic but ...
Date: Wed May  8 09:11:02 2002	[thread overview]
Message-ID: <064b01c1f69a$71b9c100$070414ac@Home.PIN.LU> (raw)
In-Reply-To: Pine.LNX.4.33.0205081213340.3518-100000@diablo.unixag-zw.fh-kl.de

Hi!

> What i would like  is a solution which is between LVM and a RAIDx. LVM
> has in my eyes the disadvantage that you create a filesystem over
different
> drives/partitions. If you lose one you nearly lose everything.
> With a RAID you lose a harddrive/partition (diskspace) to build it (more
> costs for harddrives and maybe a controller).

here's what you/one could do:
- you create a RAID5 occupying about 10% of your total disk space
- you create a a PV on this RAID5 and disable allocation on it (-x n)
- you create PVs in the remaining space on all the disks
- you put all the PVs in a VG
- you create your partitions
- you have faith in pvmove ;-)

Finally you'll need a script which runs regularly and uses the statistics
from lvdisplay to find out which PEs are most read from and written to and
moves those PEs to the PV which is on the RAID5.  This is very likely to
keep at least all the metadata of your filesystems on the RAID5 part of your
disks since metadata should have the most accesses.  Additionally one could
add some magic to the filesystems which allows finding out where the
metadata is and lock those PEs onto the RAID5-PV.

I'm too chicken to have faith in pvmove ;-)

     christian

  parent reply	other threads:[~2002-05-08  9:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-08  0:03 [linux-lvm] VG wiederfinden Tim-Christian.Hanschen
2002-05-08  6:46 ` Heinz J . Mauelshagen
2002-05-08  7:44 ` [linux-lvm] offtopic but Oliver Jovic
2002-05-08  7:48   ` Tim
2002-05-08  8:11     ` Oliver Jovic
2002-05-08  8:23       ` Tim
2002-05-08  9:11         ` Oliver Jovic
2002-05-08 11:20           ` Ragnar Kjørstad
2002-05-10  8:46           ` Heinz J . Mauelshagen
2002-05-08  9:11   ` Christian Limpach [this message]
2002-05-08  9:27     ` Steven Lembark
2002-05-13  4:37       ` Harri Haataja
2002-05-13  4:42         ` Patrick Caulfield
2002-05-13  7:37           ` Tim
2002-05-13  9:39             ` Steven Lembark
2002-05-13 10:21               ` Benjamin Scott
2002-05-13 15:32                 ` Goetz Bock
2002-05-13 18:54                   ` Benjamin Scott
2002-05-14  7:17                     ` Goetz Bock
2002-05-14  7:46                       ` Steven Lembark
2002-05-14  8:08                         ` Benjamin Scott
2002-05-14  8:13                           ` Tim
2002-05-13  9:29         ` Steven Lembark
2002-05-13 10:19           ` Benjamin Scott
2002-05-13 10:30             ` Steven Lembark

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='064b01c1f69a$71b9c100$070414ac@Home.PIN.LU' \
    --to=chris@pin.lu \
    --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