Can't work this out. The golden client and target client are the same.
Both have a 160GB SATA hard drive. On the golden client I get the
following when I run 'sfdisk -s -l /dev/sda':
156250000
Disk /dev/sda: 19452 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from
0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ 3 4- 32098+ de Dell Utility
/dev/sda2 4 15033 15030 120728475 83 Linux
/dev/sda3 * 15034 15046 13 104422+ 83 Linux
/dev/sda4 15047 19451 4405 35383162+ 5 Extended
/dev/sda5 15047+ 19451 4405- 35383131 8e Linux LVM
Doing the same on the target client after it stops with the
'Insufficient free extents' error I get:
156250000
Disk /dev/sda: 19452 cylinders, 255 tracks, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from
0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ 3- 4- 30273 83 Linux
/dev/sda2 3+ 14337- 14334- 115135742+ 83 Linux
/dev/sda3 * 14337+ 14349- 13- 99609+ 83 Linux
/dev/sda4 14349+ 19452- 5103- 40984374+ 5 Extended
/dev/sda5 14349+ 19452- 5103- 40984374 8e Linux LVM
How come the numbers are different?
In the install script the commands to create the LVM are:
### BEGIN LVM initialization commands -AR- ###
logmsg "Initializing partition /dev/sda5 for use by LVM."
logmsg "pvcreate -M2 -ff -y /dev/sda5 || shellout"
pvcreate -M2 -ff -y /dev/sda5 || shellout
### END LVM initialization commands ###
### BEGIN LVM groups creation commands -AR- ###
logmsg "lvremove -f /dev/VolGroup_ID_25535 >/dev/null 2>&1 && vgremove
VolGroup_ID_25535 >/dev/null 2>&1"
lvremove -f /dev/VolGroup_ID_25535 >/dev/null 2>&1 && vgremove
VolGroup_ID_25535 >/dev/null 2>&1
logmsg "vgcreate -M2 -l 0 -p 0 -s 32768K VolGroup_ID_25535 ${DISK0}5 ||
shellout"
vgcreate -M2 -l 0 -p 0 -s 32768K VolGroup_ID_25535 ${DISK0}5 || shellout
### END LVM groups creation commands ###
### BEGIN LVM volumes creation commands -AR- ###
logmsg "lvcreate -L1998848K -n LogVol1 VolGroup_ID_25535 || shellout"
lvcreate -L1998848K -n LogVol1 VolGroup_ID_25535 || shellout
logmsg "lvscan > /dev/null; lvchange -a y /dev/VolGroup_ID_25535/LogVol1
|| shellout"
lvscan > /dev/null; lvchange -a y /dev/VolGroup_ID_25535/LogVol1 ||
shellout
logmsg "lvcreate -L31522816K -n LogVol3 VolGroup_ID_25535 || shellout"
lvcreate -L31522816K -n LogVol3 VolGroup_ID_25535 || shellout
logmsg "lvscan > /dev/null; lvchange -a y /dev/VolGroup_ID_25535/LogVol3
|| shellout"
lvscan > /dev/null; lvchange -a y /dev/VolGroup_ID_25535/LogVol3 ||
shellout
logmsg "lvcreate -L1769472K -n LogVol0 VolGroup_ID_25535 || shellout"
lvcreate -L1769472K -n LogVol0 VolGroup_ID_25535 || shellout
logmsg "lvscan > /dev/null; lvchange -a y /dev/VolGroup_ID_25535/LogVol0
|| shellout"
lvscan > /dev/null; lvchange -a y /dev/VolGroup_ID_25535/LogVol0 ||
shellout
logmsg "lvcreate -L118816768K -n LogVolHome VolGroup_ID_25535 ||
shellout"
lvcreate -L118816768K -n LogVolHome VolGroup_ID_25535 || shellout
logmsg "lvscan > /dev/null; lvchange -a y
/dev/VolGroup_ID_25535/LogVolHome || shellout"
lvscan > /dev/null; lvchange -a y /dev/VolGroup_ID_25535/LogVolHome ||
shellout
### END LVM volumes creation commands ###
I'm using version 3.7.3-1 of Systemimager on both the golden client and
the server.
Thanks
Zubin
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrea
Righi
Sent: Saturday, 17 June 2006 1:04 AM
To: [email protected]
Subject: Re: [Sisuite-users] blockdev and insmod errors
Sethna, Zubin wrote:
> You are correct the script fails after the modprobe command with the
> following:
>
> lvcreate -L118816768K -n LogVolHome VolGroup_ID_25535 || shellout
> Insufficient free extents (173) in volume group VolGroup_ID_25535:
> 3626
Here is the problem... there are not enough extents in the volume group
VolGroup_ID_25535 to create the logical volume LogVolHome.
Option 1: there's not enough space in the disk - can you check the disk
size in the target client?
Option 2: try to increase the extent size, changing the attribute
phys_extent_size in
/var/lib/systemimager/images/<image_name>/etc/systemimager/autoinstallsc
ript.conf.
Then run again si_mkautoinstallscript. But I'm not sure if this last
option can resolve...
Regards,
-Andrea
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
