All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Marcus <CMarcus@Media-Brokers.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Adding PVs to a group
Date: Mon, 21 Apr 2008 06:04:17 -0400	[thread overview]
Message-ID: <480C66A1.9030909@Media-Brokers.com> (raw)
In-Reply-To: <480BC65A.1080605@gmail.com>

On 4/20/2008, David Robinson (zxvdr.au@gmail.com) wrote:
>> OT: this list seems a little on the dead side... is there a more 
>> active LVM oriented list that you are aware of?

> The list is active, but its quiet on weekends ;)

Oh, right, I forget that some people actually have lives outside work, 
unlike me... ;)

> You could modify the partition table in one step rather than two. Use 
> fdisk to delete both partitions then create a new partition that 
> spans the entire device (just make sure that you create the partition 
> with the same start block). The end result should look something like:
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdb1               1       58352   468712408+  8e  Linux LVM

I have read about doing this, but somehow it just gives me the shudders...

I'll have to play with it sometime in a VM...

>> resize /dev/sdb1, reboot, then

> You may not need to reboot at all... you could use "partprobe" or 
> "blockdev --rereadpt", but check /proc/partitions to make sure that 
> the kernel knows of the new partition table. I've seen instances 
> where partprobe doesn't actually cause the partition table to be 
> refreshed.

Thanks - have to read up on partprobe too...

Still feel like a newbie sometimes, even though I've been using Linux 
for almost two years now (came over from the windows world)...

>> So, again - does it really matter? Is having my vg2 in one big LVM 
>> partition 'better' than having it consist of two different partitions?

> There's no difference, LVM doesn't care.

Ok, thanks... thats what I'll do for now... I'm actually planning on 
replacing this server with a different one and rebuilding everything 
from scratch in a few months anyway, so I'll redo the partitions then...

For now, simple and safe is best... my main goal is to keep /var from 
filling up...

-- 

Best regards,

Charles

  reply	other threads:[~2008-04-21 10:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 21:45 [linux-lvm] Adding PVs to a group Charles Marcus
2008-04-18 21:51 ` Charles Marcus
2008-04-19  0:18   ` dave
2008-04-21 10:16     ` Bryn M. Reeves
2008-04-21 12:51       ` Charles Marcus
2008-04-19 17:57 ` Charles Marcus
2008-04-20  3:19   ` David Robinson
2008-04-20 16:42     ` Charles Marcus
2008-04-20 22:40       ` David Robinson
2008-04-21 10:04         ` Charles Marcus [this message]
2008-04-21  0:22       ` Ross Boylan
2008-04-21 10:06         ` Charles Marcus

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=480C66A1.9030909@Media-Brokers.com \
    --to=cmarcus@media-brokers.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 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.