linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Eric A. Hall" <ehall@ehsco.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM questions
Date: Thu, 29 Mar 2007 11:55:44 -0500	[thread overview]
Message-ID: <460BEF90.60900@ehsco.com> (raw)


Hi guys,

I'm putting together a storage server for NAS and iSCSI purposes and am
looking to use LVM for some or all of this. I've read up on LVM but I
still have some basic newbie questions for this.

I've got a bunch of Raptor 150 ADFD drives and a 3Ware 9650SE board
providing the basic back-end storage (currently RAID-5 but will move to
RAID-6 soon, with estimated capacity of approx 800-900 GB, although the
entire array may shrink or grow as projects demand). The opsys root
partition will be about 40 GB XFS, with another 4GB swap partition, and
the NAS/storage pool will be about 300 GB XFS, with the remainder of the
space being used by the iSCSI volumes (about another 300 GB, divvied up
among different iSCSI LUNs). I want to be able to shrink and expand these
by about 10 GB per (although swap may only change by +/-4GB) so I figure
I'll use LVM for all of the partitions. A couple of other considerations
here: I need to align the partitions on page boundaries for iSCSI
performance reasons, and I am also thinking about managing blockdev
read-ahead differently for each of the final volumes.

I assume that a single physical extent across /dev/sda will work as well
as anything else here. Will having more partitions make it easier to
shrink and expand the whole RAID if that ever becomes necessary? Anything
else I should take into consideration?

Should I create a single volume group or should I create multiple volume
groups, or does it even matter? What are the issues?

I have seen some people talk about creating hundreds of small partitions
and using those for moving and resizing. Is this needed, desirable, or
just a stupid human trick?

Anything else I should take into consideration here would be appreciated

Thanks!

             reply	other threads:[~2007-03-29 16:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 16:55 Eric A. Hall [this message]
2007-03-29 17:38 ` [linux-lvm] LVM questions Stuart D. Gathman
2007-04-20 13:36   ` Nix
  -- strict thread matches above, loose matches on Subject: below --
2008-03-27 22:27 [linux-lvm] LVM Questions Nicholas Muguira
2008-04-02  8:20 ` Jordi Prats
2001-05-03  0:48 Darren Young
2001-05-03  1:26 ` Glenn Shannon
2001-05-03  1:45 ` Evan Day
2001-05-03  6:56   ` Adrian Phillips
2001-05-04  9:33     ` Heinz J. Mauelshagen
2001-05-04  7:45       ` Adrian Phillips
2001-05-04 10:38         ` Heinz J. Mauelshagen
2001-05-04  9:38           ` Adrian Phillips
2001-05-04 13:39             ` Heinz J. Mauelshagen
2001-05-03 11:15   ` Heinz J. Mauelshagen
2001-05-03 11:41 ` Carlo Marcelo Arenas Belon
2001-05-04  1:59   ` Mark van Walraven

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=460BEF90.60900@ehsco.com \
    --to=ehall@ehsco.com \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).