From: Galen Seitz <galens@seitzassoc.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] N00b Question: Logical Volume without a Logical Volume Group ?
Date: Wed, 02 Nov 2011 10:57:09 -0700 [thread overview]
Message-ID: <4EB18475.5040202@seitzassoc.com> (raw)
In-Reply-To: <825955434.1696549.1320246372085.JavaMail.root@sz0126a.westchester.pa.mail.comcast.net>
Dan White wrote:
> ----- James Hawtin <oolon@ankh.org> wrote:
>
> I had to reboot the machine to "see" the expanded LUN. I used fdisk
> to make a partition out of the LUN expansion, but I had to reboot
> again before I could do anything further. After the second reboot,
> I was able to make a PV out of the new partition, roll it into the
> existing VG and then expand the two test LV's I had previously
> created to utilize the new elbow room.
>
> This is on a RHEL 5.7 system.
>
> Is there a way to do this without the rebooting ?
I don't know about the first reboot(not a SAN/LUN user), but I would
expect the second reboot could be avoided by running partprobe.
--
Galen Seitz
galens@seitzassoc.com
next prev parent reply other threads:[~2011-11-02 17:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 18:39 [linux-lvm] N00b Question: Logical Volume without a Logical Volume Group ? Dan White
2011-11-01 18:45 ` Digimer
2011-11-01 19:13 ` Dan White
2011-11-01 19:20 ` Digimer
2011-11-01 19:51 ` Dan White
2011-11-02 14:02 ` Mark H. Wood
2011-11-01 21:09 ` Ray Morris
2011-11-02 10:18 ` James Hawtin
2011-11-02 11:41 ` Marek Podmaka
2011-11-02 13:37 ` James Hawtin
2011-11-02 14:18 ` Mark H. Wood
2011-11-02 14:50 ` Marek Podmaka
2011-11-02 14:56 ` James Hawtin
2011-11-02 15:06 ` Dan White
2011-11-02 16:39 ` James Hawtin
2011-11-02 17:30 ` Eugene Vilensky
2011-11-02 18:23 ` Dan White
2011-11-02 18:41 ` Dan White
2011-11-02 17:57 ` Galen Seitz [this message]
2011-11-03 6:53 ` Marek Podmaka
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=4EB18475.5040202@seitzassoc.com \
--to=galens@seitzassoc.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