* [linux-lvm] I've tried to get some support on this list about lvm
@ 2009-09-15 11:37 Hugh
2009-09-15 11:49 ` Alasdair G Kergon
0 siblings, 1 reply; 8+ messages in thread
From: Hugh @ 2009-09-15 11:37 UTC (permalink / raw)
To: linux-lvm
but I've had no responses.
I'm sure I've discovered a bug but nobody has answered my
question of offered any advice or requested any further
information.
Please look at my problem and see if there is anything which might
help me.
This is the url:
http://forums.fedoraforum.org/showthread.php?p=1263530
I'll post it here too so that if for some reason you can't access the
forum:
device-mapper: reload ioctl failed: Invalid argument Failed to
suspend LogVol00
I hope this is the right forum.
I've read hundreds of threads on this problem but they seem to be
intermittent and the resolution has been using a different kernel
version.
I'm using the latest kernel but I still have this problem
[root@fc11-64 ~]# rpm -q kernel
kernel-2.6.29.6-217.2.8.fc11.x86_64
[root@fc11-64 ~]# rpm -qa | grep lvm
lvm2-2.02.48-2.fc11.x86_64
system-config-lvm-1.1.9-1.fc11.noarch
[root@fc11-64 ~]# lvresize -v -d -L 65.9375G
/dev/VolGroup00/LogVol00
Finding volume group VolGroup00
Archiving volume group "VolGroup00" metadata (seqno 5).
Extending logical volume LogVol00 to 65.94 GB
Found volume group "VolGroup00"
Found volume group "VolGroup00"
Loading VolGroup00-LogVol00 table
device-mapper: reload ioctl failed: Invalid argument
Failed to suspend LogVol00
Creating volume group backup "/etc/lvm/backup/VolGroup00"
(seqno 6).
[root@fc11-64 ~]# lvextend -v -d -L 65.9375G
/dev/VolGroup00/LogVol00
Finding volume group VolGroup00
Archiving volume group "VolGroup00" metadata (seqno 5).
Extending logical volume LogVol00 to 65.94 GB
Found volume group "VolGroup00"
Found volume group "VolGroup00"
Loading VolGroup00-LogVol00 table
device-mapper: reload ioctl failed: Invalid argument
Failed to suspend LogVol00
Creating volume group backup "/etc/lvm/backup/VolGroup00"
(seqno 6).
Running Logical Volume Manager gui and attempting to extend the
volume results in the same error.
[root@fc11-64 ~]# pvdisplay
--- Physical volume ---
PV Name /dev/sdb2
VG Name VolGroup00
PV Size 67.93 GB / not usable 24.13 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 2173
Free PE 640
Allocated PE 1533
PV UUID eCuGyH-jV7L-Tgdg-JyYW-sWK1-ehZY-OLw0WS
</cut>
[root@fc11-64 ~]# vgdisplay
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 5
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 67.91 GB
PE Size 32.00 MB
Total PE 2173
Alloc PE / Size 1533 / 47.91 GB
Free PE / Size 640 / 20.00 GB
VG UUID 7I9mBS-xzMJ-L1fC-7IT4-ckJq-g8r3-pv333k
</cut>
[root@fc11-64 ~]# lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID ph5nOV-3cyI-fFNV-WlyQ-rDI8-dTsY-5FcWn2
LV Write Access read/write
LV Status available
# open 0
LV Size 1.97 GB
Current LE 63
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
</cut>
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID ZGiTvh-XhRo-sLk5-bkJX-U30G-xkCD-rYszvt
LV Write Access read/write
LV Status available
# open 0
LV Size 45.94 GB
Current LE 1470
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3
</cut>
[root@fc11-64 ~]# tail -3 /var/log/messages
Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18
too small for target
Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: 253:3:
linear: dm-linear: Device lookup failed
Sep 10 20:55:46 fc11-64 kernel: device-mapper: ioctl: error adding
target to table
[root@fc11-64 ~]# fdisk -l
Disk /dev/sda: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000d4599
Device Boot Start End Blocks Id System
/dev/sda1 * 1 26 204800 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 26 13054 104651423+ 8e Linux LVM
Disk /dev/sdb: 73.0 GB, 73014444032 bytes
255 heads, 63 sectors/track, 8876 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd426be2d
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 9 72261 83 Linux
/dev/sdb2 10 6266 50259352+ 8e Linux LVM
Disk /dev/dm-0: 102.9 GB, 102965968896 bytes
255 heads, 63 sectors/track, 12518 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 4194 MB, 4194304000 bytes
255 heads, 63 sectors/track, 509 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 2113 MB, 2113929216 bytes
255 heads, 63 sectors/track, 257 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/dm-3: 49.3 GB, 49325015040 bytes
255 heads, 63 sectors/track, 5996 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-3 doesn't contain a valid partition table
Anybody know what the problem is?
TIA,
Hugh
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] I've tried to get some support on this list about lvm
2009-09-15 11:37 [linux-lvm] I've tried to get some support on this list about lvm Hugh
@ 2009-09-15 11:49 ` Alasdair G Kergon
2009-09-17 10:59 ` Hugh
2009-09-19 6:40 ` Hugh
0 siblings, 2 replies; 8+ messages in thread
From: Alasdair G Kergon @ 2009-09-15 11:49 UTC (permalink / raw)
To: LVM general discussion and development
On Tue, Sep 15, 2009 at 09:37:44PM +1000, Hugh wrote:
> Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18
> too small for target
There's your answer: You're trying to make it bigger than the underlying
device.
Use pvs -v to check device sizes for discrepancies.
(--units s if necessary).
Alasdair
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] I've tried to get some support on this list about lvm
2009-09-15 11:49 ` Alasdair G Kergon
@ 2009-09-17 10:59 ` Hugh
2009-09-22 8:34 ` Marian Csontos
2009-09-19 6:40 ` Hugh
1 sibling, 1 reply; 8+ messages in thread
From: Hugh @ 2009-09-17 10:59 UTC (permalink / raw)
To: LVM general discussion and development
On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
> On Tue, Sep 15, 2009 at 09:37:44PM +1000, Hugh wrote:
> > Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18
> > too small for target
>
> There's your answer: You're trying to make it bigger than the underlying
> device.
>
> Use pvs -v to check device sizes for discrepancies.
> (--units s if necessary).
>
> Alasdair
Thanks, now I can see what the problem is:
[root@fc11-64 ~]# pvs -v
Scanning for physical volume names
PV VG Fmt Attr PSize PFree DevSize PV UUID
/dev/sda2 vg_fc1164 lvm2 a- 99.80G 0 99.80G qunnek-OG2y-hp2j-31J8-
J3HT-0Aye-3w2rMN
/dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G eCuGyH-jV7L-Tgdg-JyYW-
sWK1-ehZY-OLw0WS
How is this possible?
What's the solution?
How can I grow the DevSize?
Probably a better question to ask is, how can I add the unused space into the
device and then the volume?
Maybe I should provide some more background.
I have a vmware virtual disk and I have grown the disk size by 20G.
[root@fc11-64 ~]# parted -l
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sda: 107GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 210MB 210MB primary ext3 boot
2 210MB 107GB 107GB primary lvm
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sdb: 73.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary ext3 boot
2 74.0MB 51.5GB 51.5GB primary lvm
Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol00: 49.3GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 49.3GB 49.3GB ext3
Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol01: 2114MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 2114MB 2114MB linux-swap
Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_swap: 4194MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 4194MB 4194MB linux-swap
Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_root: 103GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 103GB 103GB ext3
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] I've tried to get some support on this list about lvm
2009-09-15 11:49 ` Alasdair G Kergon
2009-09-17 10:59 ` Hugh
@ 2009-09-19 6:40 ` Hugh
1 sibling, 0 replies; 8+ messages in thread
From: Hugh @ 2009-09-19 6:40 UTC (permalink / raw)
To: linux-lvm
On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
> On Tue, Sep 15, 2009 at 09:37:44PM +1000, Hugh wrote:
> > Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18
> > too small for target
>
> There's your answer: You're trying to make it bigger than the underlying
> device.
>
> Use pvs -v to check device sizes for discrepancies.
> (--units s if necessary).
>
> Alasdair
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
This makes no sense to me Alasdair.
This may be the error message but it defies explanation.
I still think there is something wrong with the lvm sine it's the one throwing
the error and everything else seems normal.:
[root@fc11-64 ~]# pvs -v
Scanning for physical volume names
PV VG Fmt Attr PSize PFree DevSize PV UUID
/dev/sda2 vg_fc1164 lvm2 a- 99.80G 0 99.80G qunnek-OG2y-hp2j-31J8-
J3HT-0Aye-3w2rMN
/dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G eCuGyH-jV7L-Tgdg-JyYW-
sWK1-ehZY-OLw0WS
[root@fc11-64 ~]# pvscan
PV /dev/sdb2 VG VolGroup00 lvm2 [67.91 GB / 20.00 GB free]
PV /dev/sda2 VG vg_fc1164 lvm2 [99.80 GB / 0 free]
Total: 2 [167.71 GB] / in use: 2 [167.71 GB] / in no VG: 0 [0 ]
Perhaps I just don't know how to interpret the output but it appears to be
normal and I don't know what to do next.
I'm desperate to recover my old fc9 disk, any suggestions or step by step
guides which might point out where I went wrong or what the actual problem
might be?
Thank, Hugh
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] I've tried to get some support on this list about lvm
2009-09-17 10:59 ` Hugh
@ 2009-09-22 8:34 ` Marian Csontos
2009-09-22 13:18 ` Hugh
0 siblings, 1 reply; 8+ messages in thread
From: Marian Csontos @ 2009-09-22 8:34 UTC (permalink / raw)
To: LVM general discussion and development
Hugh wrote:
> On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
>
>> On Tue, Sep 15, 2009 at 09:37:44PM +1000, Hugh wrote:
>>
>>> Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18
>>> too small for target
>>>
>> There's your answer: You're trying to make it bigger than the underlying
>> device.
>>
>> Use pvs -v to check device sizes for discrepancies.
>> (--units s if necessary).
>>
>> Alasdair
>>
>
> Thanks, now I can see what the problem is:
>
> [root@fc11-64 ~]# pvs -v
> Scanning for physical volume names
> PV VG Fmt Attr PSize PFree DevSize PV UUID
> /dev/sda2 vg_fc1164 lvm2 a- 99.80G 0 99.80G qunnek-OG2y-hp2j-31J8-
> J3HT-0Aye-3w2rMN
> /dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G eCuGyH-jV7L-Tgdg-JyYW-
> sWK1-ehZY-OLw0WS
>
>
> How is this possible?
> What's the solution?
> How can I grow the DevSize?
> Probably a better question to ask is, how can I add the unused space into the
> device and then the volume?
>
>
Hi Hugh,
taking into account this:
> Maybe I should provide some more background.
> I have a vmware virtual disk and I have grown the disk size by 20G.
>
and...
> [root@fc11-64 ~]# parted -l
> Model: VMware, VMware Virtual S (scsi)
> Disk /dev/sda: 107GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
>
> Number Start End Size Type File system Flags
> 1 32.3kB 210MB 210MB primary ext3 boot
> 2 210MB 107GB 107GB primary lvm
>
>
> Model: VMware, VMware Virtual S (scsi)
> Disk /dev/sdb: 73.0GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
>
>
...this:
> Number Start End Size Type File system Flags
> 1 32.3kB 74.0MB 74.0MB primary ext3 boot
> 2 74.0MB 51.5GB 51.5GB primary lvm
>
>
you have to resize sdb2 partition first.
Though I do not understand why it is possible to resize PV beyond end of
device (doing that should display a warning message, but command will
pass), this is definitely not a LVM bug.
HTH,
-- Marian
> Model: Linux device-mapper (dm)
> Disk /dev/mapper/VolGroup00-LogVol00: 49.3GB
> Sector size (logical/physical): 512B/512B
> Partition Table: loop
>
> Number Start End Size File system Flags
> 1 0.00B 49.3GB 49.3GB ext3
>
>
> Model: Linux device-mapper (dm)
> Disk /dev/mapper/VolGroup00-LogVol01: 2114MB
> Sector size (logical/physical): 512B/512B
> Partition Table: loop
>
> Number Start End Size File system Flags
> 1 0.00B 2114MB 2114MB linux-swap
>
>
> Model: Linux device-mapper (dm)
> Disk /dev/mapper/vg_fc1164-lv_swap: 4194MB
> Sector size (logical/physical): 512B/512B
> Partition Table: loop
>
> Number Start End Size File system Flags
> 1 0.00B 4194MB 4194MB linux-swap
>
>
> Model: Linux device-mapper (dm)
> Disk /dev/mapper/vg_fc1164-lv_root: 103GB
> Sector size (logical/physical): 512B/512B
> Partition Table: loop
>
> Number Start End Size File system Flags
> 1 0.00B 103GB 103GB ext3
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] I've tried to get some support on this list about lvm
2009-09-22 8:34 ` Marian Csontos
@ 2009-09-22 13:18 ` Hugh
2009-09-22 16:07 ` malahal
2009-09-22 16:13 ` Marian Csontos
0 siblings, 2 replies; 8+ messages in thread
From: Hugh @ 2009-09-22 13:18 UTC (permalink / raw)
To: LVM general discussion and development
On Tuesday 22 September 2009 18:34:19 Marian Csontos wrote:
> Hugh wrote:
> > On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
> >> On Tue, Sep 15, 2009 at 09:37:44PM +1000, Hugh wrote:
> >>> Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18
> >>> too small for target
> >>
> >> There's your answer: You're trying to make it bigger than the underlying
> >> device.
> >>
> >> Use pvs -v to check device sizes for discrepancies.
> >> (--units s if necessary).
> >>
> >> Alasdair
> >
> > Thanks, now I can see what the problem is:
> >
> > [root@fc11-64 ~]# pvs -v
> > Scanning for physical volume names
> > PV VG Fmt Attr PSize PFree DevSize PV UUID
> > /dev/sda2 vg_fc1164 lvm2 a- 99.80G 0 99.80G
> > qunnek-OG2y-hp2j-31J8- J3HT-0Aye-3w2rMN
> > /dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G
> > eCuGyH-jV7L-Tgdg-JyYW- sWK1-ehZY-OLw0WS
> >
> >
> > How is this possible?
> > What's the solution?
> > How can I grow the DevSize?
> > Probably a better question to ask is, how can I add the unused space into
> > the device and then the volume?
>
> Hi Hugh,
>
> taking into account this:
> > Maybe I should provide some more background.
> > I have a vmware virtual disk and I have grown the disk size by 20G.
>
> and...
>
> > [root@fc11-64 ~]# parted -l
> > Model: VMware, VMware Virtual S (scsi)
> > Disk /dev/sda: 107GB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: msdos
> >
> > Number Start End Size Type File system Flags
> > 1 32.3kB 210MB 210MB primary ext3 boot
> > 2 210MB 107GB 107GB primary lvm
> >
> >
> > Model: VMware, VMware Virtual S (scsi)
> > Disk /dev/sdb: 73.0GB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: msdos
>
> ...this:
> > Number Start End Size Type File system Flags
> > 1 32.3kB 74.0MB 74.0MB primary ext3 boot
> > 2 74.0MB 51.5GB 51.5GB primary lvm
>
> you have to resize sdb2 partition first.
>
> Though I do not understand why it is possible to resize PV beyond end of
> device (doing that should display a warning message, but command will
> pass), this is definitely not a LVM bug.
>
> HTH,
>
> -- Marian
>
> > Model: Linux device-mapper (dm)
> > Disk /dev/mapper/VolGroup00-LogVol00: 49.3GB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: loop
> >
> > Number Start End Size File system Flags
> > 1 0.00B 49.3GB 49.3GB ext3
> >
> >
> > Model: Linux device-mapper (dm)
> > Disk /dev/mapper/VolGroup00-LogVol01: 2114MB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: loop
> >
> > Number Start End Size File system Flags
> > 1 0.00B 2114MB 2114MB linux-swap
> >
> >
> > Model: Linux device-mapper (dm)
> > Disk /dev/mapper/vg_fc1164-lv_swap: 4194MB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: loop
> >
> > Number Start End Size File system Flags
> > 1 0.00B 4194MB 4194MB linux-swap
> >
> >
> > Model: Linux device-mapper (dm)
> > Disk /dev/mapper/vg_fc1164-lv_root: 103GB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: loop
> >
> > Number Start End Size File system Flags
> > 1 0.00B 103GB 103GB ext3
> >
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
Thank Marian,
Any idea how to resize sdb2? It's lvm and maybe I could delete it and recreate
it with fdisk but maybe it will break and everything will be lost.
Hugh
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] I've tried to get some support on this list about lvm
2009-09-22 13:18 ` Hugh
@ 2009-09-22 16:07 ` malahal
2009-09-22 16:13 ` Marian Csontos
1 sibling, 0 replies; 8+ messages in thread
From: malahal @ 2009-09-22 16:07 UTC (permalink / raw)
To: linux-lvm
Hugh [whobedobe@dodo.com.au] wrote:
> Any idea how to resize sdb2? It's lvm and maybe I could delete it and
> recreate it with fdisk but maybe it will break and everything will be
> lost.
>
> Hugh
You should be able to use fdisk to delete the partition first and then
create a new one with bigger size. MAKE SURE that the new partition's
start sector is same as the old one.
Thanks, Malahal.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] I've tried to get some support on this list about lvm
2009-09-22 13:18 ` Hugh
2009-09-22 16:07 ` malahal
@ 2009-09-22 16:13 ` Marian Csontos
1 sibling, 0 replies; 8+ messages in thread
From: Marian Csontos @ 2009-09-22 16:13 UTC (permalink / raw)
To: LVM general discussion and development
Hugh wrote:
> On Tuesday 22 September 2009 18:34:19 Marian Csontos wrote:
>
>> Hugh wrote:
>>
>>> On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
>>>
>>>> On Tue, Sep 15, 2009 at 09:37:44PM +1000, Hugh wrote:
>>>>
>>>>> Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18
>>>>> too small for target
>>>>>
>>>> There's your answer: You're trying to make it bigger than the underlying
>>>> device.
>>>>
>>>> Use pvs -v to check device sizes for discrepancies.
>>>> (--units s if necessary).
>>>>
>>>> Alasdair
>>>>
>>> Thanks, now I can see what the problem is:
>>>
>>> [root@fc11-64 ~]# pvs -v
>>> Scanning for physical volume names
>>> PV VG Fmt Attr PSize PFree DevSize PV UUID
>>> /dev/sda2 vg_fc1164 lvm2 a- 99.80G 0 99.80G
>>> qunnek-OG2y-hp2j-31J8- J3HT-0Aye-3w2rMN
>>> /dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G
>>> eCuGyH-jV7L-Tgdg-JyYW- sWK1-ehZY-OLw0WS
>>>
>>>
>>> How is this possible?
>>> What's the solution?
>>> How can I grow the DevSize?
>>> Probably a better question to ask is, how can I add the unused space into
>>> the device and then the volume?
>>>
>> Hi Hugh,
>>
>> taking into account this:
>>
>>> Maybe I should provide some more background.
>>> I have a vmware virtual disk and I have grown the disk size by 20G.
>>>
>> and...
>>
>>
>>> [root@fc11-64 ~]# parted -l
>>> Model: VMware, VMware Virtual S (scsi)
>>> Disk /dev/sda: 107GB
>>> Sector size (logical/physical): 512B/512B
>>> Partition Table: msdos
>>>
>>> Number Start End Size Type File system Flags
>>> 1 32.3kB 210MB 210MB primary ext3 boot
>>> 2 210MB 107GB 107GB primary lvm
>>>
>>>
>>> Model: VMware, VMware Virtual S (scsi)
>>> Disk /dev/sdb: 73.0GB
>>> Sector size (logical/physical): 512B/512B
>>> Partition Table: msdos
>>>
>> ...this:
>>
>>> Number Start End Size Type File system Flags
>>> 1 32.3kB 74.0MB 74.0MB primary ext3 boot
>>> 2 74.0MB 51.5GB 51.5GB primary lvm
>>>
>> you have to resize sdb2 partition first.
>>
>> Though I do not understand why it is possible to resize PV beyond end of
>> device (doing that should display a warning message, but command will
>> pass), this is definitely not a LVM bug.
>>
>> HTH,
>>
>> -- Marian
>>
>>
>>> Model: Linux device-mapper (dm)
>>> Disk /dev/mapper/VolGroup00-LogVol00: 49.3GB
>>> Sector size (logical/physical): 512B/512B
>>> Partition Table: loop
>>>
>>> Number Start End Size File system Flags
>>> 1 0.00B 49.3GB 49.3GB ext3
>>>
>>>
>>> Model: Linux device-mapper (dm)
>>> Disk /dev/mapper/VolGroup00-LogVol01: 2114MB
>>> Sector size (logical/physical): 512B/512B
>>> Partition Table: loop
>>>
>>> Number Start End Size File system Flags
>>> 1 0.00B 2114MB 2114MB linux-swap
>>>
>>>
>>> Model: Linux device-mapper (dm)
>>> Disk /dev/mapper/vg_fc1164-lv_swap: 4194MB
>>> Sector size (logical/physical): 512B/512B
>>> Partition Table: loop
>>>
>>> Number Start End Size File system Flags
>>> 1 0.00B 4194MB 4194MB linux-swap
>>>
>>>
>>> Model: Linux device-mapper (dm)
>>> Disk /dev/mapper/vg_fc1164-lv_root: 103GB
>>> Sector size (logical/physical): 512B/512B
>>> Partition Table: loop
>>>
>>> Number Start End Size File system Flags
>>> 1 0.00B 103GB 103GB ext3
>>>
>>>
>>> _______________________________________________
>>> linux-lvm mailing list
>>> linux-lvm@redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-lvm
>>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>
>>
>
> Thank Marian,
>
> Any idea how to resize sdb2?
Easy. Just search web for:
linux resize partition
Or check these direct links:
command line GNU parted: http://www.gnu.org/software/parted/index.shtml
GNOME gparted: http://gparted.sourceforge.net/
KDE qtparted: ...
> It's lvm and maybe I could delete it and recreate
> it with fdisk but maybe it will break and everything will be lost.
>
Marian
> Hugh
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2009-09-22 16:13 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-15 11:37 [linux-lvm] I've tried to get some support on this list about lvm Hugh
2009-09-15 11:49 ` Alasdair G Kergon
2009-09-17 10:59 ` Hugh
2009-09-22 8:34 ` Marian Csontos
2009-09-22 13:18 ` Hugh
2009-09-22 16:07 ` malahal
2009-09-22 16:13 ` Marian Csontos
2009-09-19 6:40 ` Hugh
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).