* [linux-lvm] [LVM] Extending LV
@ 2011-09-22 12:32 Michaël Berger
2011-09-22 12:46 ` Michaël Berger
0 siblings, 1 reply; 3+ messages in thread
From: Michaël Berger @ 2011-09-22 12:32 UTC (permalink / raw)
To: linux-lvm
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
Hello,
I am very new to LVM. Trying to extend a LV after I added a 4th disk in a HW
RAID, but I don't have much luck. I am really hoping someone out there can
help me.
Here is my setup:
[root@sk-nas ~]# fdisk /dev/cciss/c0d0
The number of cylinders for this disk is set to 53535.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/cciss/c0d0: 440.3 GB, 440345714688 bytes
255 heads, 63 sectors/track, 53535 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 13 104391 83 Linux
/dev/cciss/c0d0p2 14 35690 286575502+ 8e Linux LVM
Command (m for help):
As one can see /dev/cciss/c0d0 is now 440.3GB, which means that my 4th disk
is "physically" seen in the array. so far so good.
First issue, looks like the 4th disk in not seen by pvscan?
[root@sk-nas ~]# pvscan
PV /dev/cciss/c0d0p2 VG VolGroup00 lvm2 [273.28 GB / 0 free]
Total: 1 [273.28 GB] / in use: 1 [273.28 GB] / in no VG: 0 [0 ]
[root@sk-nas ~]#
[root@sk-nas ~]# pvdisplay
--- Physical volume ---
PV Name /dev/cciss/c0d0p2
VG Name VolGroup00
PV Size 273.30 GB / not usable 18.89 MB
Allocatable yes (but full)
PE Size (KByte) 32768
Total PE 8745
Free PE 0
Allocated PE 8745
PV UUID 07qmA3-5eD9-klBa-OzWp-XDz1-pUvX-KGXAji
[root@sk-nas ~]#
What should I do, looks like my first disk is not seen by lvm?
Thanks!
Michael
[-- Attachment #2: Type: text/html, Size: 2032 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] [LVM] Extending LV
2011-09-22 12:32 [linux-lvm] [LVM] Extending LV Michaël Berger
@ 2011-09-22 12:46 ` Michaël Berger
2011-09-23 14:34 ` Ray Morris
0 siblings, 1 reply; 3+ messages in thread
From: Michaël Berger @ 2011-09-22 12:46 UTC (permalink / raw)
To: linux-lvm
[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]
aha: that is something:
Command (m for help): v
286690436 unallocated sectors
Command (m for help): n
Probably I need to add that the c0d0p2 with fdisk first
On Thu, Sep 22, 2011 at 2:32 PM, Michaël Berger <miberger79@gmail.com>wrote:
> Hello,
>
> I am very new to LVM. Trying to extend a LV after I added a 4th disk in a
> HW RAID, but I don't have much luck. I am really hoping someone out there
> can help me.
>
> Here is my setup:
>
> [root@sk-nas ~]# fdisk /dev/cciss/c0d0
>
> The number of cylinders for this disk is set to 53535.
> There is nothing wrong with that, but this is larger than 1024,
> and could in certain setups cause problems with:
> 1) software that runs at boot time (e.g., old versions of LILO)
> 2) booting and partitioning software from other OSs
> (e.g., DOS FDISK, OS/2 FDISK)
>
> Command (m for help): p
>
> Disk /dev/cciss/c0d0: 440.3 GB, 440345714688 bytes
> 255 heads, 63 sectors/track, 53535 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/cciss/c0d0p1 * 1 13 104391 83 Linux
> /dev/cciss/c0d0p2 14 35690 286575502+ 8e Linux LVM
>
> Command (m for help):
>
> As one can see /dev/cciss/c0d0 is now 440.3GB, which means that my 4th disk
> is "physically" seen in the array. so far so good.
>
> First issue, looks like the 4th disk in not seen by pvscan?
>
> [root@sk-nas ~]# pvscan
> PV /dev/cciss/c0d0p2 VG VolGroup00 lvm2 [273.28 GB / 0 free]
> Total: 1 [273.28 GB] / in use: 1 [273.28 GB] / in no VG: 0 [0 ]
> [root@sk-nas ~]#
>
> [root@sk-nas ~]# pvdisplay
> --- Physical volume ---
> PV Name /dev/cciss/c0d0p2
> VG Name VolGroup00
> PV Size 273.30 GB / not usable 18.89 MB
> Allocatable yes (but full)
> PE Size (KByte) 32768
> Total PE 8745
> Free PE 0
> Allocated PE 8745
> PV UUID 07qmA3-5eD9-klBa-OzWp-XDz1-pUvX-KGXAji
>
> [root@sk-nas ~]#
>
> What should I do, looks like my first disk is not seen by lvm?
>
> Thanks!
>
> Michael
>
[-- Attachment #2: Type: text/html, Size: 2548 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] [LVM] Extending LV
2011-09-22 12:46 ` Michaël Berger
@ 2011-09-23 14:34 ` Ray Morris
0 siblings, 0 replies; 3+ messages in thread
From: Ray Morris @ 2011-09-23 14:34 UTC (permalink / raw)
To: linux-lvm
> aha: that is something:
>
>
> Command (m for help): v
> 286690436 unallocated sectors
>
> Command (m for help): n
>
> Probably I need to add that the c0d0p2 with fdisk first
You could enlarge c0d0p2, but LVM makes that unnecesary. You can just
add c0d0p3, run pvcreate on it:
pvcreate /dev/cciss/c0d0p3
then:
vgextend VolGroup00 /dev/cciss/c0d0p3
Since all of the partitions end up in the pool called VolGroup00
anyway, it makes no difference if there's one large paritition or
two smaller ones. Once they are part of VolGroup00 you just work
with the group without ever thinking about partitions again.
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On Thu, 22 Sep 2011 14:46:08 +0200
Michaël Berger <miberger79@gmail.com> wrote:
> aha: that is something:
>
>
> Command (m for help): v
> 286690436 unallocated sectors
>
> Command (m for help): n
>
> Probably I need to add that the c0d0p2 with fdisk first
>
> On Thu, Sep 22, 2011 at 2:32 PM, Michaël Berger
> <miberger79@gmail.com>wrote:
>
> > Hello,
> >
> > I am very new to LVM. Trying to extend a LV after I added a 4th
> > disk in a HW RAID, but I don't have much luck. I am really hoping
> > someone out there can help me.
> >
> > Here is my setup:
> >
> > [root@sk-nas ~]# fdisk /dev/cciss/c0d0
> >
> > The number of cylinders for this disk is set to 53535.
> > There is nothing wrong with that, but this is larger than 1024,
> > and could in certain setups cause problems with:
> > 1) software that runs at boot time (e.g., old versions of LILO)
> > 2) booting and partitioning software from other OSs
> > (e.g., DOS FDISK, OS/2 FDISK)
> >
> > Command (m for help): p
> >
> > Disk /dev/cciss/c0d0: 440.3 GB, 440345714688 bytes
> > 255 heads, 63 sectors/track, 53535 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> >
> > Device Boot Start End Blocks Id
> > System /dev/cciss/c0d0p1 * 1 13 104391
> > 83 Linux /dev/cciss/c0d0p2 14 35690
> > 286575502+ 8e Linux LVM
> >
> > Command (m for help):
> >
> > As one can see /dev/cciss/c0d0 is now 440.3GB, which means that my
> > 4th disk is "physically" seen in the array. so far so good.
> >
> > First issue, looks like the 4th disk in not seen by pvscan?
> >
> > [root@sk-nas ~]# pvscan
> > PV /dev/cciss/c0d0p2 VG VolGroup00 lvm2 [273.28 GB / 0
> > free] Total: 1 [273.28 GB] / in use: 1 [273.28 GB] / in no VG: 0
> > [0 ] [root@sk-nas ~]#
> >
> > [root@sk-nas ~]# pvdisplay
> > --- Physical volume ---
> > PV Name /dev/cciss/c0d0p2
> > VG Name VolGroup00
> > PV Size 273.30 GB / not usable 18.89 MB
> > Allocatable yes (but full)
> > PE Size (KByte) 32768
> > Total PE 8745
> > Free PE 0
> > Allocated PE 8745
> > PV UUID 07qmA3-5eD9-klBa-OzWp-XDz1-pUvX-KGXAji
> >
> > [root@sk-nas ~]#
> >
> > What should I do, looks like my first disk is not seen by lvm?
> >
> > Thanks!
> >
> > Michael
> >
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-09-23 14:34 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-22 12:32 [linux-lvm] [LVM] Extending LV Michaël Berger
2011-09-22 12:46 ` Michaël Berger
2011-09-23 14:34 ` Ray Morris
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.