As further confirmation, I've just tested an install on an armel box with
Colin's patch, and it worked nicely there, too.
- Matt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I can confirm that Colin's patch of Tue, 21 Oct 2008 22:57:45 +0100 fixes
the problem for me on a test install on amd64. I tested by building parted
and then putting the udeb into localudebs and putting it into the initrd.
- Matt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On Tuesday 21 October 2008, Colin Watson wrote:
> Maybe something like this?
Thanks for the patch. I'll give it a try tomorrow.
If that is correct, we can probably remove a few tests for loop devices in
partman:
- partman-base/choose_partition/partition_tree/do_option: 55
- partman-base/parted_s
On Tue, Oct 21, 2008 at 09:02:57PM +0200, Frans Pop wrote:
> On Tuesday 21 October 2008, Colin Watson wrote:
> > That may be the proximate cause, but at most it's just exposing
> > breakage elsewhere. The actual incorrect code is in libparted itself,
> > not parted_server. It should not be generati
On Tuesday 21 October 2008, Colin Watson wrote:
> That may be the proximate cause, but at most it's just exposing
> breakage elsewhere. The actual incorrect code is in libparted itself,
> not parted_server. It should not be generating "p1"-type device names
> for LVM logical volumes.
Problem is th
Hi,
On Tue, Oct 21, 2008 at 06:16:46PM +0200, Frans Pop wrote:
> The cause looks to be a recent change by Colin Watson in partman-base
> (128). If I rebuild parted_server without that change, I can no longer
> reproduce the error.
Interesting. We at least had a few successful installations wher
On Tue, Oct 21, 2008 at 06:16:46PM +0200, Frans Pop wrote:
> On Saturday 18 October 2008, Jeroen Dekkers wrote:
> > I currently have the same problem. The reason the logical volume is in
> > use seems to be that when you finish partitioning and partman goes to
> > the stage of creating the filesyst
On Saturday 18 October 2008, Jeroen Dekkers wrote:
> I currently have the same problem. The reason the logical volume is in
> use seems to be that when you finish partitioning and partman goes to
> the stage of creating the filesystems, the system has suddenly created
> partitions on top of the vol
I have the same problem, including the partitions on top
of the logical volumes:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502432
I asked to mark my bug as "duplicate" or something.
greez
Mario
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble?
On Sun, Oct 19, 2008 at 12:20:34AM +0200, Marc Haber wrote:
> On Sat, Oct 18, 2008 at 06:01:12PM +0200, Jeroen Dekkers wrote:
> > I currently have the same problem. The reason the logical volume is in
> > use seems to be that when you finish partitioning and partman goes to
> > the stage of creatin
On Sat, Oct 18, 2008 at 06:01:12PM +0200, Jeroen Dekkers wrote:
> I currently have the same problem. The reason the logical volume is in
> use seems to be that when you finish partitioning and partman goes to
> the stage of creating the filesystems, the system has suddenly created
> partitions on t
I currently have the same problem. The reason the logical volume is in
use seems to be that when you finish partitioning and partman goes to
the stage of creating the filesystems, the system has suddenly created
partitions on top of the volumes. That means there is a
/dev/mapper/vg0-homep1, which u
severity 502618 serious
thanks
On Saturday 18 October 2008, Marc Haber wrote:
> When saying "Finish partitioning and write changes to disk", the
> installer says "The ext3 file system creation in partition #1 of LVM
> VG vg0, LV home failed", and syslog says "Oct 18 11:45:27 partman:
> /dev/mapper
Processing commands for [EMAIL PROTECTED]:
> severity 502618 serious
Bug#502618: partman: /dev/mapper/vg0-home is apparently in use by the system
Severity set to `serious' from `important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
Processing commands for [EMAIL PROTECTED]:
> reassign 502618 partman-lvm
Bug#502618: partman: /dev/mapper/vg0-home is apparently in use by the system
Bug reassigned from package `installation-reports' to `partman-lvm'.
>
End of message, stopping processing here.
Please contac
Package: installation-reports
Severity: important
Trying to install lenny on a physical machine which has already one
Windows partition, using today's daily image.
Intended disk layout:
│ LVM VG vg0, LV home - 40.0 GB Linux device-mapper (linear) │
│ > #140.0
16 matches
Mail list logo
