Your message dated Mon, 8 Mar 2010 16:58:47 +0000
with message-id <20100308165847.ga2...@riva.ucam.org>
and subject line Re: Bug#512740: Sparc disk labels broken on LDOM and Parallel
installs
has caused the Debian Bug report #512740,
regarding Sparc disk labels broken on LDOM and Parallel installs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
512740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: parted
Architecture: i386
Version: 1.8.8.git.2008.03.24-11.1
Severity: grave
Tags: patch
I was exposed to this bug while trying to do a second install of
Debian into an LDOM, but its not the only way to trigger it...
Parted currently has a bug where if you try to install to more than
one disk at once (2 parallel installs), or on LDOM you try to install
more than one LDOM which has a physical disk as a backing device,
parted will trash the disk label, rendering the disk unusable until
you go and relabel it with the 'format' command in solaris.
Ubuntu got around this by applying a patch (written by David S. Miller
and Fabio M. Di Nitto who happen to do a lot of work on the sparc
Linux port). This applies cleanly against the current Lenny source
package for parted (which means that the udeb can be rebuilt and
installs will be fixed. From the patch description:
## sparc-new-label.dpatch by David S. Miller and
## Fabio M. Di Nitto <fabbi...@ubuntu.com>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Fix sparc disk label generation. This is required for LDOM and
## DP: parallel installations with Solaris 10.
I've attached this as it applies cleanly so there's little maintainer
work (hopefully).
I've set the severity to grave as it causes data loss on the disk
you're installing on (if youre already using some partitions on that
disk for something else). It also blocks install if its the second
disk you've installed Debian on (feel free to correct me!).
Thanks,
Mike.
--- End Message ---
--- Begin Message ---
Source: parted
Source-Version: 2.2-1
(Note that this is still in NEW, and is currently targeted at
experimental but we plan to move it to unstable soon; I'm
version-closing it while I remember.)
On Tue, Feb 09, 2010 at 06:54:39PM +0100, Frans Pop wrote:
> I've read through the patch, but must admit I don't understand it. What
> seems to be missing is *how* exactly it fixes the problem.
>
> And somehow I doubt this patch stands on its own. I would think that it is
> a requirement for patches in other packages (such as partman). If that is
> true, then testing the patch in isolation is not much use (as applying it
> on its own would not fix the reported issue anyway).
>
> Also, I question the definition of (unused?) tags for usr, var, home etc.
> What's the purpose of that? How's that supposed to be used? Does it mean
> you're not allowed to put e.g. /srv on a separate partition as there's no
> tag for it?
In all honesty, the only reason I hadn't dropped this patch from Ubuntu
long ago was that I felt I'd have had to sit there and try to understand
it otherwise. It definitely modified far more than it needed to in
order to get the job done, and as far as I know the original authors
never sent it upstream.
I'm not aware of any partman changes that were associated with this
change in Ubuntu.
Anyway, the patch non-trivially failed to apply on top of parted 2.2-1,
which forced the issue a bit, so I went and looked at it in more detail
than I had done previously, starting by stripping out non-essential
parts of the patch (renamed structures, added #defines, etc.). It
turned out that there was nothing left! The actual important part of
this change was applied upstream in 2.2, with this NEWS entry:
sun: the version, sanity and nparts VTOC fields were ignored by libparted.
Those fields are properly initialized now. The nparts (number of partitions)
field is initialized to 8 (max. number of sun partitions) rather that to a
real number of partitions. This solution is compatible with Linux kernel
and Linux fdisk.
Thus I've dropped this patch from Ubuntu, with some relief, and we can
consider it fixed in Debian once parted 2.2-1 lands.
Cheers,
--
Colin Watson [cjwat...@debian.org]
--- End Message ---
