[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#462396: marked as done (Multiple disks support for partman-auto-lvm)

Your message dated Mon, 25 Aug 2008 19:32:05 +0000
with message-id <E1KXhnJ-000220-Sw@ries.debian.org>
and subject line Bug#462396: fixed in partman-auto-lvm 29
has caused the Debian Bug report #462396,
regarding Multiple disks support for partman-auto-lvm
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 owner@bugs.debian.org
immediately.)


-- 
462396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462396
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: partman-auto-lvm
Version: 26
Severity: wishlist

Hi,

I finally managed to write a more general patch[1] to have multiple disks 
support in partman-auto-lvm. It has been successfully tested on x86 with
the  three base recipes of the installer (atomic, home and multi) to
prevent  regressions, and with four homebrew recipes that show what you
can do with  it.

This patch is based on the current (as of 2008/01/24) SVN version of 
partman-auto and partman-auto-lvm (the former needing only a minor 
modification).

A little note about how to use this patch : it is currently available only
 using preseeding. To do this, you must preseed three things :
- partman-auto/expert_recipe_file : nothing new here ;
- partman-auto/disk : the first disk, known from now as the default one.
This  is not mandatory, but may prevent bad surprises ;
- partman-auto-lvm/extra_devices : a new entry in which you declare all
extra  devices that will be available to partman-auto-lvm. You must at
least add  here all devices used in the recipe. Devices not used in the
recipe and  declared here will be silently ignored.

Now here is a description of the four recipes I wrote, and that must cover
all  use cases supported by this patch, with informations about new
attributes  available. All of these recipes use two disks (hda and hdb),
but it should  work with more (a bug in QEmu prevented me from using hdd,
but I hope I'll  can test it on VMWare on another machine).

The first recipe[2] creates two volume groups, vg00 and vg01, respectively
on  hda and hdb, plus a /boot partition. vg00 is used for all LV except
/home,  created on vg01.

In it you can see all the new attributes and their use :
- device{ } is used when declaring a new PV on a specific device. In this 
example, device is /dev/hda, but it can also be a partition as you'll see
in  the third recipe. If device is empty, the default device is used ; -
vgname{ } is used to declare of which VG the PV will be a member of. If 
vgname is empty, the default one will be used ;
- invg{ } is used to create a LV on a specific VG. If invg is empty, it is
 created on the default one.

The second recipe[3] is roughly the same as the first, with a minor change
:  no VG is declared for the LVs except /home. In this case, a default VG
(whose  name is the hostname of the machine) is created and all LVs that
don't have a  invg{ } declaration will be created on this one. Of course,
this VG must have  a free device available to be created on. But more on
the errors after the  recipes.

The third recipe[4] creates a single VG, with a given name, out of two 
partitions on the devices. The rest is simple to understand if you read
the  first two recipes : all LVs are created on a single VG, vg00,
declared on the  PVs hda2 and hdb1. I put a big, red, flashing warning
here : it's not because  you said "use hda2 and hdb1 to create this VG"
that these partitions will be  created. No, you must guess what the
partitions numbers will be based on the  behavior of partman-auto-lvm.
With the recent patch of Frans Pop, default PV  will always be created on
a primary partition. With your recipe it's on your  own to guess.

The fourth recipe[5] is the same as the third, except the PVs will be
added to  the default VG (whose name is the hostname of the machine) as
there's no  vgname and invg attributes.

OK, now about the errors that you can have. I added two debconf templates
in  partman-auto-lvm :
- partman-auto-lvm/no_such_pv : this means that the recipe contains a 
reference to a PV that doesn't exist. This is the case if it's not
declared  in partman-auto-lvm/extra_devices, or if it hasn't been
detected, or if you  didn't guessed correctly the partitioning ;
- partman-auto-lvm/no_pv_in_vg : happens if a VG was declared but that no
PV  could be associated with. For example it could happen if you forgot a
invg{ }  declaration on a LV (which then triggers the need for the default
VG), and if  there's no device without a vgname{ } attribute. But it's not
limited to this  case, and this error is a Bad News.

OK, I think it's all for now. If you have any question or if you found a
bug  I'll happily try to help. I hope you'll find this patch useful.

Cheers,
Grégory

[1] : http://ogre.nerim.net/d-i/partman-auto-lvm_20080124.diff
[2] : http://ogre.nerim.net/d-i/testrecipe-01
[3] : http://ogre.nerim.net/d-i/testrecipe-02
[4] : http://ogre.nerim.net/d-i/testrecipe-03
[5] : http://ogre.nerim.net/d-i/testrecipe-04

--- End Message ---
--- Begin Message --- 
Source: partman-auto-lvm
Source-Version: 29

We believe that the bug you reported is fixed in the latest version of
partman-auto-lvm, which is due to be installed in the Debian FTP archive:

partman-auto-lvm_29.dsc
  to pool/main/p/partman-auto-lvm/partman-auto-lvm_29.dsc
partman-auto-lvm_29.tar.gz
  to pool/main/p/partman-auto-lvm/partman-auto-lvm_29.tar.gz
partman-auto-lvm_29_all.udeb
  to pool/main/p/partman-auto-lvm/partman-auto-lvm_29_all.udeb



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 462396@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Bobbio <lunar@debian.org> (supplier of updated partman-auto-lvm 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Mon, 25 Aug 2008 21:05:34 +0200
Source: partman-auto-lvm
Binary: partman-auto-lvm
Architecture: source all
Version: 29
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Jérémy Bobbio <lunar@debian.org>
Description: 
 partman-auto-lvm - Automatically partition storage devices using LVM (udeb)
Closes: 385220 462396 484272
Changes: 
 partman-auto-lvm (29) unstable; urgency=low
 .
   [ Christian Perrier ]
   * Add translation sublevel markers to debconf templates.
 .
   [ Jérémy Bobbio ]
   * Use convert_to_megabytes() in auto_lvm_prepare().
     Depends: partman-base (>= 125)
   * Replace $devfs_pvdevices by $pv_devices in auto_lvm_prepare() and remove
     devfs resolving in autopartition-lvm.
     Depends: partman-auto (>= 81)
   * Call get_last_free_partition_infos() after auto_init_disk().
     Depends: partman-auto (>= 81)
   * Use auto_init_disks() instead of auto_init_disk().
     Depends: partman-auto (>= 81)
   * Add support for preseeding logical volume names directly using
     lv_name{ <name> } in the recipe.  (Closes: #484272)
   * Add support for preseeding multiple disks, specifiying explicit partitions
     to hold Physical Volumes, specifying Volume Group names and specifiying
     in which VG Logical Volumes should be created.  (Closes: #385220, #462396)
     Based on a patch by Grégory Oestreicher.
 .
   [ Updated translations ]
   * Arabic (ar.po) by Ossama M. Khayat
   * Bulgarian (bg.po) by Damyan Ivanov
   * Czech (cs.po) by Miroslav Kure
   * Dzongkha (dz.po) by Jurmey Rabgay(Bongop) (DIT,BHUTAN)
   * Greek, Modern (el.po) by Emmanuel Galatoulas
   * Basque (eu.po) by Piarres Beobide
   * Finnish (fi.po) by Esko Arajärvi
   * French (fr.po) by Christian Perrier
   * Galician (gl.po) by Jacobo Tarrio
   * Gujarati (gu.po) by Kartik Mistry
   * Italian (it.po) by Milo Casagrande
   * Japanese (ja.po) by Kenshi Muto
   * Kurdish (ku.po) by Erdal Ronahi
   * Lithuanian (lt.po) by Kęstutis Biliūnas
   * Malayalam (ml.po) by Praveen|പ്രവീണ്‍ A|എ
   * Marathi (mr.po) by Sampada
   * Norwegian Bokmål (nb.po) by Hans Fredrik Nordhaug
   * Portuguese (pt.po) by Miguel Figueiredo
   * Portuguese (Brazil) (pt_BR.po) by Felipe Augusto van de Wiel (faw)
   * Romanian (ro.po) by Eddy Petrișor
   * Russian (ru.po) by Yuri Kozlov
   * Slovak (sk.po) by Ivan Masár
   * Swedish (sv.po) by Daniel Nylander
   * Thai (th.po) by Theppitak Karoonboonyanan
   * Turkish (tr.po) by Mert Dirik
   * Traditional Chinese (zh_TW.po) by Tetralet
Checksums-Sha1: 
 833f19a16e35d13549edc4c96104f760ec5fcdcd 923 partman-auto-lvm_29.dsc
 7fec92eb89d262b643fb7c8a982af7764d18efce 73534 partman-auto-lvm_29.tar.gz
 2259f7dc32098ba28edbdfd5c563590c473f04af 48880 partman-auto-lvm_29_all.udeb
Checksums-Sha256: 
 e36754d7ffffe6d908a4c7db9314aa531bbca554fd9147000971d16b76b672f8 923 partman-auto-lvm_29.dsc
 56b33a8e7a45a260b2510b6515089895012ca09d0cc23dcf86be358a42716e49 73534 partman-auto-lvm_29.tar.gz
 70a6cd22146e70f1da4d7b5d1d0543b7cce3a7d5909ab577370aa1dcbc05bdc0 48880 partman-auto-lvm_29_all.udeb
Files: 
 4f67decc5a0d71e1ccf3eab692eff604 923 debian-installer optional partman-auto-lvm_29.dsc
 c48f1b56d9611ea4f1bb9f53b8755af2 73534 debian-installer optional partman-auto-lvm_29.tar.gz
 fa66db0c1c371085af90234c97692d3d 48880 debian-installer optional partman-auto-lvm_29_all.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIswcP2PUjs9fQ72URAlFYAJ0WrEP1DoDhvJjJpa6RDm2umMkVRACgpiWQ
OBhVFrpPQDbsGjHQkzuMSOo=
=rc97
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: