We're using systemimager 3.2.0.4, we noticed that the clients' partition type for the swap partition is being set to "83" instead of the normal "82":

da235:~>fdisk -l /dev/cciss/c0d0

Disk /dev/cciss/c0d0: 72.8 GB, 72833679360 bytes
255 heads, 32 sectors/track, 17433 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes

           Device Boot Start    End    Blocks   Id  System
/dev/cciss/c0d0p1   *      1     38    155024   83  Linux
/dev/cciss/c0d0p2         39  16919  68874480   83  Linux
/dev/cciss/c0d0p3      16920  17433   2097120   83  Linux

It still seems to work ok:

da235:~>swapon -s
Filename               Type            Size    Used    Priority
/dev/cciss/c0d0p3      partition       2097112 42552   -1

It seems that the master script is defaulting to "ext2" for all partitions in parted. This seems to come from the following line from /usr/lib/systemimager/perl/SystemImager/Server.pm:

 $cmd = qq(parted -s -- $devfs_dev mkpart $p_type{$m} ext2 ) .
                q($START_MB $END_MB) . qq( || shellout);

I'm wondering if having the swap partition's type set to "83" might cause problems for the client? Is this an oversight on the part of SI, or am I missing something?

Cheers,

Paul

P.S. I just checked SI version 3.2.3-1, and the same ext2 default
     still seems to apply with that version.

--
Paul Robertson
Email: [EMAIL PROTECTED]
Phone: 617-784-1575
GnuPG Public Key: http://unixway.com/misc/pgpkey.txt


------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to