From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Right way to resize LVM Volume on SAN?
Date: Thu, 8 Jun 2006 21:56:51 +0200 [thread overview]
Message-ID: <20060608195651.GF548@percy.comedia.it> (raw)
In-Reply-To: <44882ED2.4050806@alienworld.org>
On Thu, Jun 08, 2006 at 04:06:10PM +0200, Alen Salamun wrote:
>Thank you. I read that already. And since it only says:
>
>"Expand the PV on /dev/sda1 AFTER enlarging the partition with fdisk"
>
>my question is related on part of enlarging partition with fdisk. Do I
>have to do it in described way (delete, create new with extended last
>sector) to preserve data or is there any other "less destructive
>look-a-like" way?
sfdisk for backing up your partition table
parted to resize
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2006-06-08 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 8:53 [linux-lvm] Right way to resize LVM Volume on SAN? Alen Salamun
2006-06-08 9:42 ` Heinz Mauelshagen
2006-06-08 14:06 ` Alen Salamun
2006-06-08 19:56 ` Luca Berra [this message]
2006-06-09 7:36 ` Zac Slade
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=20060608195651.GF548@percy.comedia.it \
--to=bluca@comedia.it \
--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