linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Jorge Fábregas" <jorge.fabregas@gmail.com>
To: LVM Mailingliste <linux-lvm@redhat.com>
Subject: [linux-lvm] Extend VG - Expand LUN vs New Disk
Date: Mon, 21 Dec 2015 08:30:29 -0400	[thread overview]
Message-ID: <5677F0E5.5050101@gmail.com> (raw)

Hi everyone,

Are there any major differences between expanding an existing LUN
(already striped & mirrored on storage-array) and use pvresize &
"lvextend -r ..." vs adding a new disk to your VG when you need to
expand an existing filesystem?

At work we do the latter and almost everyone believes expanding an
existing LUN is not a safe operation.  Is there really a preferred
method? Or is it just a matter of personal preference?

Thanks!
Jorge

             reply	other threads:[~2015-12-21 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 12:30 Jorge Fábregas [this message]
2015-12-21 12:50 ` [linux-lvm] Extend VG - Expand LUN vs New Disk Bryn M. Reeves
2015-12-21 16:13   ` Jorge Fábregas

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=5677F0E5.5050101@gmail.com \
    --to=jorge.fabregas@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).