From: mmclinn@cdt.com
To: linux-lvm@msede.com
Subject: [linux-lvm] LVM Question
Date: Wed, 08 Sep 1999 10:24:15 -0400 [thread overview]
Message-ID: <37D6718F.D3D86A09@cdt.com> (raw)
Hello,
First off, I'm a big supporter of LVM, I use it on a 56gig array at home
regularly without any problems and I can't wait to see it migrate into
the stable kernel tree.
I do have a couple of questions for people with more experience than
I...
I am currently preparing to setup a new main file server for my company.
It will be linux based, and will store approximately 25 gigs of data
that
will be used constantly. LVM would be _really_ useful on this machine.
I'm wondering peoples opinions about whether or not LVM is ready to be
used in
a business environment. In other words, how stable has this code been
for people?
I have run into no problems, but I have been using it informally thus
far.
Also, I am wondering whether or not future versions of LVM will always
be compatible with the current implementation? Will there ever be a
point when I would need to
reinstall my LVM volumes to upgrade to the latest version of LVM?
Any opinions, thoughts, cautions, advice, ect.. would be much
appreciated.
Thanks all!
-Michael McLinn
next reply other threads:[~1999-09-08 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-08 14:24 mmclinn [this message]
1999-09-08 18:17 ` [linux-lvm] LVM Question Brian Wolfe
1999-09-08 19:28 ` S. Ryan Quick
-- strict thread matches above, loose matches on Subject: below --
2003-06-19 16:11 Jay Lee
2003-06-19 16:36 ` bscott
2003-10-15 15:56 [linux-lvm] LVM question John Diana
2005-03-04 12:49 [linux-lvm] LVM Question Matthias Rudolph
2005-03-04 22:35 ` Mark W. Jeanmougin
2005-03-05 9:23 ` Luca Berra
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=37D6718F.D3D86A09@cdt.com \
--to=mmclinn@cdt.com \
--cc=linux-lvm@msede.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 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.