Bugs item #1397885, was opened at 2006-01-05 10:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1397885&group_id=259
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Allen Bierbaum (allenb)
Assigned to: Nobody/Anonymous (nobody)
Summary: Invalid parted sizes with skipped partition
Initial Comment:
I imaged a machine that had a partition table like this:
Disk geometry for /dev/sda: 0.000-238475.179 megabytes
Disk label type: msdos
Minor Start End Type Filesystem Flags
1 0.031 2047.346 primary linux-swap
3 82019.355 182017.705 primary ext3
Notice that there is no partition 2. When systemimager
created the autoinstaller script for this it ended up
with invalid disk sizes like:
logmsg "Creating partition ${DISK0}1."
START_MB=$END_OF_LAST_PRIMARY
END_MB=$(echo "scale=3; ($START_MB + 2047)" | bc)
logmsg "parted -s -- $DISK0 mkpart primary ext2
$START_MB $END_MB || shellout"
parted -s -- $DISK0 mkpart primary ext2 $START_MB
$END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB
logmsg "Creating partition ${DISK0}2."
START_MB=$(( $DISK_SIZE - 1 ))
END_MB=$(( $DISK_SIZE - 0 ))
logmsg "parted -s -- $DISK0 mkpart primary ext2
$START_MB $END_MB || shellout"
parted -s -- $DISK0 mkpart primary ext2 $START_MB
$END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB
logmsg "Creating partition ${DISK0}3."
START_MB=$END_OF_LAST_PRIMARY
END_MB=$(( $DISK_SIZE - 2 ))
logmsg "parted -s -- $DISK0 mkpart primary ext2
$START_MB $END_MB || shellout"
parted -s -- $DISK0 mkpart primary ext2 $START_MB
$END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB
The problem here is with the second partition where the
start is size-1 and the end is size-0. This is invalid
since there is no second partition and it throws off
the start of the size for the 3rd partition.
For now you can work around this bug by just not
imaging disks that are missing partitions. (ie. I
added a small second partition and things worked fine).
-Allen
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1397885&group_id=259
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
