* ralonso@lis.state.oh.us <ralonso@lis.state.oh.us> [Jul 09. 2002 17:43]:
It turns out the problem I was having had nothing to do with SCSI or RAID. What happened was that my partitioning scheme was something along the lines of this: sda5: 512M sda6: 512M swap sda7: 2048M sda8: max <--- here's the problem sda9: 2048M
The way I was using 'max' was that it allots the remaining space to its partition after ALL other partitions have been accounted for. Apparently, what actually happens is that it allots the remaining space taking into account only those partitions that have already been defined. This means that if you specify a 'max' partition it must always be last. Because all the space had already been allotted, YaST complained that the partition table was invalid. I think it'd be beneficial to allow a 'max' partition to be anywhere in the partitioning order. I imagine it'd probably be pretty easy to implement in code. I'd do it myself but I haven't seen any source code for this project.
'max' does only make sense if you are using it with the last partition. Of course it is also possible to make it work with other partitions but that is not planned right now. Another negative effect is for example if you try to set 'max' on two partitions on the same drive... YaST2 source is available in the distribution and even without the having the source, you still can modify things if you want. It is script based as some of you might have noticed.... Anas
Thanks, Robert
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada