From: "Javier de Miguel Rodríguez" <javier.miguel@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Question about hardware LVM
Date: Thu, 2 Feb 2006 22:08:27 +0100 [thread overview]
Message-ID: <7cce3190602021308n184bcc43m@mail.gmail.com> (raw)
Hello
I have been successfully using LVM on RedHat Linux Server with no
hassle. We are now deploying a $BIGVENDOR expensive FiberChannel SAN.
One of the main features of this SAN is that is able to grow a
filesystem
How does Linux handle this? Do I still have to use LVM? If I still
have to use LVM I do NOT see the point of "hardware base growing".
Simply, create a new LUN in the SAN and I can join to our LVM setup.
Maybe this is a "Storage 101" questio, but I do not fully understand
expensive SAN "hardware based" filesystem grow.
Thank you in advance
next reply other threads:[~2006-02-02 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 21:08 Javier de Miguel Rodríguez [this message]
2006-02-02 22:01 ` [linux-lvm] Question about hardware LVM Ming Zhang
2006-02-03 5:41 ` Zac Slade
2006-02-03 13:58 ` Ming Zhang
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=7cce3190602021308n184bcc43m@mail.gmail.com \
--to=javier.miguel@gmail.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).