I get the overall concepts but not the details and I think I may have
found a problem. In the first section, there is partition information
with sections like "num=1", "num=2", etc.... and I can see where those
map to partitions numbers on the physical disks. Further, the size is
either a specific number or * to use the rest of the disk. So on my
system which has a parition table of:
8 0 71132000 sda
8 1 104391 sda1
8 2 66557295 sda2
8 3 4466070 sda3
8 16 71132000 sdb
8 19 8001 sdb3
it only makes sense that for the first disk I see:
<part num="1" size="101.944" p_type="primary" p_name="-"
flags="boot" />
<part num="2" size="64997.358" p_type="primary" p_name="-"
flags="-" />
<part num="3" size="*" p_type="primary" p_name="-" flags="-" />
and for the second:
<part num="3" size="*" p_type="primary" p_name="-" flags="-" />
BUT somehow this gets turned into an installation script and I think
there's a bug here because my script tries to create 3 partitions for
the second disk, each being very small and starting at the end of the
disk, resulting in the following code in the installation script:
logmsg "Creating partition ${DISK1}1."
START_MB=$(( $DISK_SIZE - 3 ))
END_MB=$(( $DISK_SIZE - 2 ))
logmsg "parted -s -- $DISK1 mkpart primary $START_MB $END_MB || shellout"
parted -s -- $DISK1 mkpart primary $START_MB $END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB
logmsg "Creating partition ${DISK1}2."
START_MB=$(( $DISK_SIZE - 1 ))
END_MB=$(( $DISK_SIZE - 0 ))
logmsg "parted -s -- $DISK1 mkpart primary $START_MB $END_MB || shellout"
parted -s -- $DISK1 mkpart primary $START_MB $END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB
logmsg "Creating partition ${DISK1}3."
START_MB=$END_OF_LAST_PRIMARY
END_MB=$(( $DISK_SIZE - 4 ))
logmsg "parted -s -- $DISK1 mkpart primary $START_MB $END_MB || shellout"
parted -s -- $DISK1 mkpart primary $START_MB $END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB
and this turns into the command to create partions in the range of 73836
to 72837, 72838 to 72839 and 72839 to 72835!!!
Then, my installation script blows up because of overlapping
partitions. In fact if I print out the partition table at that point I
see 2 partitions both starting at 73GB and ending at 73GB. totally
nonsensical. whether or not this relates to previous problems I've been
reporting I haven't a clue but it sure feels like something is very wrong.
-mark
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
