Your message dated Sat, 18 Jun 2005 08:47:17 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#314459: fixed in ggcov 0.3-3
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Jun 2005 12:25:36 +0000
>From [EMAIL PROTECTED] Thu Jun 16 05:25:36 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.physik.uni-muenchen.de [192.54.42.129]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DitR9-0002E7-00; Thu, 16 Jun 2005 05:25:35 -0700
Received: from localhost (unknown [127.0.0.1])
by mail.physik.uni-muenchen.de (Postfix) with ESMTP id 4EC9A2001A
for <[EMAIL PROTECTED]>; Thu, 16 Jun 2005 14:25:34 +0200 (CEST)
Received: from mail.physik.uni-muenchen.de ([127.0.0.1])
by localhost (mail.physik.uni-muenchen.de [127.0.0.1]) (amavisd-new, port
10024)
with LMTP id 28369-02-35 for <[EMAIL PROTECTED]>;
Thu, 16 Jun 2005 14:25:32 +0200 (CEST)
Received: from mailhost.cip.physik.uni-muenchen.de
(kaiser.cip.physik.uni-muenchen.de [141.84.136.1])
by mail.physik.uni-muenchen.de (Postfix) with ESMTP id 250AE2000D
for <[EMAIL PROTECTED]>; Thu, 16 Jun 2005 14:25:32 +0200 (CEST)
Received: from eiger.cip.physik.uni-muenchen.de
(eiger.cip.physik.uni-muenchen.de [141.84.136.54])
by mailhost.cip.physik.uni-muenchen.de (Postfix) with ESMTP id
6F80926E89
for <[EMAIL PROTECTED]>; Thu, 16 Jun 2005 14:25:31 +0200 (CEST)
Received: by eiger.cip.physik.uni-muenchen.de (Postfix, from userid 3092)
id 743AD176CE; Thu, 16 Jun 2005 14:25:31 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
by eiger.cip.physik.uni-muenchen.de (Postfix) with ESMTP id 6EAAF22151
for <[EMAIL PROTECTED]>; Thu, 16 Jun 2005 14:25:31 +0200 (CEST)
Date: Thu, 16 Jun 2005 14:25:31 +0200 (CEST)
From: Thomas Fischbacher <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: lvmcreate_initrd fails to create working initrds
Message-ID: <[EMAIL PROTECTED]>
X-BOFH: Daemons did it
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: amavisd-new at physik.uni-muenchen.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: lvm10
Version: 1.0.8-8
Severity: critical
Problem description:
lvm10 is the logical volume manager userspace utility package for the
official 2.4 kernel series. When setting up a system which has its root
partition on LVM, the kernel has to be loaded from a non-LVM boot
partition (which the bootloader can handle), together with an initrd that
contains
/sbin/vgscan
/sbin/vgchange -a y
in its linuxrc to detect and initialize the LVM partitions. Only after
this, / can be moved to LVM.
the lvmcreate_initrd utility is supposed to create a ramdisk image that
does precisely this job. If this ever worked as advertised, it seems as if
the behaviour of vgscan/vgchange changed in a way not respected by
lvmcreate_initrd. In particular, either vgscan or vgchange tries to write
a considerable amount of temporary data into the ramdisk, more than it can
handle, which causes partition detection to fail.
Effect: it is not possible to disk-boot a system with / installed on LVM.
This presumably justifies the rating of this bug as "critical". (One may
argue that / never should be on LVM, however, (1) the official
documentation does not explicitly state so, (2) there are situations where
snapshotting for / is highly desirable.)
Solution:
The initrd created by lvmcreate_initrd should be a (compressed) ext2 image
of about 6 MB (uncompressed) size, created with increased inode density
(mke2fs -i 1024), containing everything from the image created by the
broken lvmcreate_initrd, as well as a directory etc/lvmtab.d - with such
an initrd, LVM detection and boot will work.
For completeness, here is a working GRUB menu.lst entry showing how to
boot such a system:
title Debian GNU/Linux LVM, kernel 2.4.31
root (hd0,0)
kernel /vmlinuz-2.4.31 root=3a05 ro vga=ext ramdisk_size=8192
initrd /initrd-lvm-2.4.30-repaired-manually.gz
savedefault
boot
Notes:
(*) It does not work to give part of the kernel args in the 'kernel' line,
and others (like ramdisk_size) in an extra 'append' line.
(*) Specifying the root= kernel parameter as [0-9a-f]{4} causes the kernel
to first look for a /dev/ entry with that name. If that fails, it tries to
boot from the device whose [major][minor] ID is the one given. LVM
usually has major ID 58, which is 3a in hex. The minor id designates the
partition and can be found out e.g. by looking into /proc/partitions of a
CD-booted system which has LVM activated.
--
regards, [EMAIL PROTECTED] (o_
Thomas Fischbacher - http://www.cip.physik.uni-muenchen.de/~tf //\
(lambda (n) ((lambda (p q r) (p p q r)) (lambda (g x y) V_/_
(if (= x 0) y (g g (- x 1) (* x y)))) n 1)) (Debian GNU)
---------------------------------------
Received: (at 314459-close) by bugs.debian.org; 18 Jun 2005 12:51:48 +0000
>From [EMAIL PROTECTED] Sat Jun 18 05:51:48 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Djcnc-0001eu-00; Sat, 18 Jun 2005 05:51:48 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DjcjF-0007bS-00; Sat, 18 Jun 2005 08:47:17 -0400
From: Alastair McKinstry <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#314459: fixed in ggcov 0.3-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 18 Jun 2005 08:47:17 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: ggcov
Source-Version: 0.3-3
We believe that the bug you reported is fixed in the latest version of
ggcov, which is due to be installed in the Debian FTP archive:
ggcov_0.3-3.dsc
to pool/main/g/ggcov/ggcov_0.3-3.dsc
ggcov_0.3-3.tar.gz
to pool/main/g/ggcov/ggcov_0.3-3.tar.gz
ggcov_0.3-3_i386.deb
to pool/main/g/ggcov/ggcov_0.3-3_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry <[EMAIL PROTECTED]> (supplier of updated ggcov package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 18 Jun 2005 13:35:31 +0100
Source: ggcov
Binary: ggcov
Architecture: source i386
Version: 0.3-3
Distribution: unstable
Urgency: low
Maintainer: Alastair McKinstry <[EMAIL PROTECTED]>
Changed-By: Alastair McKinstry <[EMAIL PROTECTED]>
Description:
ggcov - Graphical tool for displaying gcov test coverage data
Closes: 314459
Changes:
ggcov (0.3-3) unstable; urgency=low
.
* Build on kfreebsd-i386. Closes: #314459.
Files:
d4ef1d965c9ff64a65759cd9b27eff41 572 devel optional ggcov_0.3-3.dsc
38bbb7c93cb0128f0af856fe665439b7 217589 devel optional ggcov_0.3-3.tar.gz
dc045c21e6b3372e671ed74c8adbe73a 150640 devel optional ggcov_0.3-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCtBYvQTK/kCo4XFcRAk+VAKCP+qZoztfN2ZmawHqsJ2WLYmynpgCguzeE
Jel4jZn942C8FGpWdLdsXRA=
=dmCF
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
