Severe partitioning bugs in AY 10.0RC1
Hi,
I already read about the other problem with partition in RC1, but I think
the problems I have are different. It seems that the partition_nr statement
is completely ignored:
This profile
<partitioning config:type="list">
<drive>
<device>/dev/hda</device>
<partitions config:type="list">
<partition>
<create config:type="boolean">true</create>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
<fstopt>defaults</fstopt>
<mount>swap</mount>
On Wednesday 21 September 2005 11:45, Frank Steiner wrote:
This profile
<partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>swap</mount>
2 <size>1gb</size> </partition> </partitions> <use>all</use> </drive> </partitioning>should result in a hard disk with just /dev/hda2 as swap. But it creates /dev/hda1 as swap.
okay, I never tried something like that. I'm not so sure that this worked on
SUSE Linux 9.3 but anyway, please add:
So at the moment, partitioning is almost impossible with 10.0RC1 :-)
then you can call me the partitioning wizard. Making the impossible happen ;) -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Uwe Gansert wrote
okay, I never tried something like that. I'm not so sure that this worked on SUSE Linux 9.3 but anyway, please add:
1 in the <drive> section.I hope I got you right, that you hava a primary partition nr. 1 that you want to keep. If you don't have a primary partition 1 and you want to start
Well, no, this was just to demonstrate that the partition_nr is ignored :-)
with a primary partition 2, without any prim. part. 1 at all, I don't think that's possible with autoyast but I really would be interested for what kind of reason you need such a strange partitioning.
Indeed we used to have this for certain hosts, because we weren't sure yet if the first partition was going to be a windows or linux partition later, so we just left the space unused. Anyway, it does work this way in 9.0 :-) Is it really difficult to make autoyast work this way? I thought that's what the partition_nr parameter is for... Telling autoyast "Shut up and do I want!" ;-))
then you can call me the partitioning wizard. Making the impossible happen ;)
I surely will if you could also solve the other two problems for us :-)
Seriously, can you say sth. about the second and third problem? autoyast
used to auto-generate an extended partition as /dev/hda4 if only
/dev/hda1-3 and /dev/hda5 were specified. That's where the partition_nr
element helped a lot, because we generate the profiles from fstab files
by scripts, and we didn't have to think about the extended partition
ourselves, autoyast just determined it by itself.
Assuming that this was lost some time between 9.0 and 10.0 (wuah, bring
it back please :-)), what about this strange behaviour when specifying
the extended partition manually? To make sure it's not caused by the
missing first partition, I used the profile listed below. Note that
without specifying the extended partition no. 4, autoyast in SuSE 9.0
will create this (which is what we expect):
/dev/hda1 /dos fat32 defaults 4gb
/dev/hda2 swap swap defaults 1gb
/dev/hda3 / ext3 defaults 15gb
/dev/hda5 /local ext3 defaults 8gb
/dev/hda6 /home ext3 defaults 20gb
However, 10.0RC1 will create this (with defining partition 4 as
extended partition; failing without it):
/dev/hda1 /dos fat32 defaults 4gb
/dev/hda2 swap swap defaults 1gb
/dev/hda3 <extended>
/dev/hda5 / ext3 defaults 15gb
/dev/hda6
On Wednesday 21 September 2005 13:50, Frank Steiner wrote:
with a primary partition 2, without any prim. part. 1 at all, I don't think that's possible with autoyast but I really would be interested for what kind of reason you need such a strange partitioning.
Indeed we used to have this for certain hosts, because we weren't sure yet if the first partition was going to be a windows or linux partition later, so we just left the space unused.
okay. I can't say if this is possible with autoyast. I did not try to have an empty space instead of the first primary until now.
Anyway, it does work this way in 9.0 :-) Is it really difficult to make autoyast work this way?
I can't say. the partitioning code in autoyast is very complex. I'll really have to fight with that beast in the near future and I keep that in mind.
Seriously, can you say sth. about the second and third problem? autoyast used to auto-generate an extended partition as /dev/hda4 if only /dev/hda1-3 and /dev/hda5 were specified.
that is still the case.
"Wizard, wizard, make it work!" ;-)
It's not that different from your version but I had to workaround a bug in
RC1 (<usepart> for partition 1) and I've added some
Oh, btw, talking about old features: autoyast1 (SuSE 6.4) used to have this feature "If I find an fstab, I reuse it and leave all partitions untouched, unless I'm told to format some". This fstab-feature was missing in 9.0 completely and came back in 9.1,
that might be. Autoyast in 10.0 is the first autoyast that I'm responsible for.
but now with the contrary behaviour: "format all partitions unless I'm told to leave some untouched". This is somewhat dangerous because you will accidentally format partitions if you forget to specify them. Couldn't this be changed so that one can chose if the default behaviour is either format-all or format-none?
hmmm. I have to take a look at that by myself to see how that works and how it behaves. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Uwe Gansert wrote
okay. I can't say if this is possible with autoyast. I did not try to have an empty space instead of the first primary until now.
Developers won't ever have a chance to imagine what crazy kind of configs the user will want to have ;-)
Seriously, can you say sth. about the second and third problem? autoyast used to auto-generate an extended partition as /dev/hda4 if only /dev/hda1-3 and /dev/hda5 were specified.
that is still the case.
Right! Your version of the profile works!
"Wizard, wizard, make it work!" ;-)
It's not that different from your version but I had to workaround a bug in RC1 (<usepart> for partition 1) and I've added some
Ok, I should have tried that myself because I read about it in the other thread, sorry!
elements to make sure autoyast has the same idea of what is primary and
Indeed it currently only works with these partition_type elements, however,
the information is redundant: If
Oh, btw, talking about old features: autoyast1 (SuSE 6.4) used to have this feature "If I find an fstab, I reuse it and leave all partitions untouched, unless I'm told to format some". This fstab-feature was missing in 9.0 completely and came back in 9.1,
that might be. Autoyast in 10.0 is the first autoyast that I'm responsible for.
I'm pretty sure this is a hard job to take over such a big project!
but now with the contrary behaviour: "format all partitions unless I'm told to leave some untouched". This is somewhat dangerous because you will accidentally format partitions if you forget to specify them. Couldn't this be changed so that one can chose if the default behaviour is either format-all or format-none?
hmmm. I have to take a look at that by myself to see how that works and how it behaves.
Thanks! cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
On Wednesday 21 September 2005 17:06, Frank Steiner wrote:
elements to make sure autoyast has the same idea of what is primary and
Indeed it currently only works with these partition_type elements, however, the information is redundant: If
is given and out of {1,2,3,4} *and* a mount point is given, then autoyast could derive it's a primary partition, because an extended partition doesn't have a mount point.
I'm not so sure about that. A partition that is not mounted into the system has no mountpoint too. hda1 might be such a candidate if it's for a windows system partition that shall not be mounted into the parallel installed linux system. All in all the partitioning is a very tricky thing, even if it sounds quite easy at first.
In the same sense, "usepart" is redundant if
is given and <create> is set to false, but I think I got you right that this is just the bug in RC1.
yes. That's fixed in the final version. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Uwe Gansert wrote
however, the information is redundant: If
is given and out of {1,2,3,4} *and* a mount point is given, then autoyast could derive it's a primary partition, because an extended partition doesn't have a mount point. I'm not so sure about that. A partition that is not mounted into the system has no mountpoint too.
Sure, this is just an "if", and not an "if and only if"! If you have partition number <= 4 and a mount point, it's a primary partition. If you are missing the mount point, you can't tell if it should be primary or extended...
All in all the partitioning is a very tricky thing, even if it sounds quite easy at first.
Definitely :-) -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
I played around a little bit with your config, trying to keep
all partitions, but even with the <usepart> workaround, I couldn't
figure out how...
I set all <create> to false, keeping <format>which still deletes and
recreates all partitions but the first. Then adding <usepart> and
On Thursday 22 September 2005 11:51, Frank Steiner wrote:
So I still am not able to keep all partitions and just format some :-(
hmmm. This looks like a bug to me. I just have finished a fix for that but it needs more testing to verify that it doesn't break something else. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
participants (2)
-
Frank Steiner
-
Uwe Gansert