public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: James Miller <jamtat@mailsnare.net>
To: linux-newbie@vger.kernel.org
Subject: LVM query
Date: Wed, 13 Oct 2004 13:58:29 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0410131346130.1347@debian-emach> (raw)

I tend to use somewhat older computers and older, smaller (and
cheaper--sometimes free!) hard drives.  As a result, I end up with 2 or
more hard drives in any given machine.  I've been manually partitioning
and usually making / the mount point for smaller of the disks, /home the
mount point for the larger (single user system, btw).  I suppose /usr
might be a good mount point for a third disk.  Be that as it may, I've
recently looked into LVM (logical volume management) and wondered whether
it might not be a better option for setting up my system.  As I understand
about the way it works, I would not run into problems such as I might have
with my former scheme--for example running out of room on / (never
happened before, but who knows).  With all disks being used as one large
filesystem under LVM--if that is, indeed, the way it works--directories
can increase to whatever size disk total allows.  So, a couple of
questions in closing: have I understood correctly how LVM works and what
it does?  Does it sound like a good solution for my scenario?  Is there
any performance hit involved in using it as over against a traditional
partitioning scheme?  Any other comments on, criticisms, praises of LVM?
Gotchas?  Thanks for any feedback on this.

James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

             reply	other threads:[~2004-10-13 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 18:58 James Miller [this message]
2004-10-13 20:15 ` LVM query Jim Nelson

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=Pine.LNX.4.58.0410131346130.1347@debian-emach \
    --to=jamtat@mailsnare.net \
    --cc=linux-newbie@vger.kernel.org \
    /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