Package: lvm2
Version: 2.02.95-6
Severity: normal

Dear Maintainer,

Installation of clvm from the sid repository currently fails unless versions 
are overridden due to the cLVM binary not having been built for the current 
upstream LVM version.
While building clvm (and enabling cluster locking in lvm2 and libs) is not a 
major issue for me, the following comment I found in the changelog is:

lvm2 (2.02.95-6) unstable; urgency=low

 * Drop cluster (clvm) support. It never properly worked and is more dead
   than alive.

-- Bastian Blank <wa...@debian.org>  Wed, 02 Jan 2013 11:11:41 +0100

A side effect of disabling this feature is removal of support for a documented 
feature (cluster locking using locking_type=2) in the config parser resulting 
in a bricked server on reboot after a package ugrade.
The maintainer may not use clvm but many of us who have built large scale 
production clusters do.
clvm works fine for me and certainly isn't dead.
Please reconsider your position concerning its distribution on Debian.


-- System Information:
Debian Release: 7.0
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lvm2 depends on:
ii  dmsetup                   2:1.02.74-6
ii  initscripts               2.88dsf-35
ii  libc6                     2.13-38
ii  libdevmapper-event1.02.1  2:1.02.74-6
ii  libdevmapper1.02.1        2:1.02.74-6
ii  libreadline5              5.2+dfsg-1
ii  libudev0                  175-7.1
ii  lsb-base                  4.1+Debian9

lvm2 recommends no packages.

lvm2 suggests no packages.

-- Configuration Files:
/etc/lvm/lvm.conf changed [not included]

-- no debconf information


This email (including any attachments) is confidential and may be privileged. 
If you have received it in error, please notify the sender by return email and 
delete this message from your system. Any unauthorised use or dissemination of 
this message in whole or in part is strictly prohibited. Please note that 
emails are susceptible to change and we will not be liable for the improper or 
incomplete transmission of the information contained in this communication nor 
for any delay in its receipt or damage to your system. We do not guarantee that 
the integrity of this communication has been maintained nor that this 
communication is free of viruses, interceptions or interference.

Reply via email to