[Rocks-Discuss] custom partitioning problems
klaus.steden at thomson.net
Wed Jun 25 18:05:46 PDT 2008
It's definitely Anaconda ... I've seen this many times with generic
RedHat/CentOS installs, more than I can count ... I'm not surprised that
ROCKS is subject to the same issue.
On 6/25/08 5:49 PM, "Brandon Davidson" <brandond at uoregon.edu>did etch on
> Greg Bruno wrote:
>> it is normal to have it labeled "/1".
>> this is being done by the anaconda installer and i can't figure out
>> how to change it. there are some messages on the internet that also
>> complain about "/1", but as far as i can tell, no one has a solution.
> It looks like Anaconda checks for conflicting labels before applying the new
> label.... although they said that disks are now labeled 'correctly', I'm not
> sure what cases this is true for.
> What seems to happen is that, if you've got a partition labeled '/' and ask to
> label a second partition the same thing ,it will append '1' to it, the third
> '2', etc. I'm betting that this happens even if you're trying to re-label the
> same partition, because the conflict check doesn't exclude the destination
> partition's from the conflict list.
> I'm curious if the state flip-flops due to this check - install N gets
> LABEL=/, install N+1 gets LABEL=/1, install N+2 gets LABEL=/ again. I could
> see this being the case because / is unique on N and N+2, but not N+1, N+3,
> etc. If this is the case then clearing the label before setting, or fixing the
> conflict check, would resolve the issue.
> On the other hand, I could be barking up the wrong tree entirely, and
> something else (like maybe one of the rocks initrds?) is stealing the / label.
> Either way, identifying conflicting uses of the / label during the Anaconda
> labeling process should tell you why it's happening.
More information about the npaci-rocks-discussion