Package: fai-setup-storage
Version: 4.0.6
Severity: important

fai-setup-storage fails when trying to do an install to a machine using
lvm when a partition is requested to be preserved. This is a regression
from fai-setup-storage 3.4.8 where this worked fine (i.e. in squeeze)

I actually believe it has a problem any time the hard disk previously
contains an lvm volumegroup, but I haven't got time to test this
configuration.

I've talked on the upstream users' mailing list a bit and there appears
to be a number of issues.

First, setup-storage depends on liblinux-lvm-perl

While that library has been redone, both versions of it just seems to
pass through the same problem.  The ultimate problem is that logical
volume information is derived from executing the "vgdisplay -v" command.

The output from this command has changed between squeeze and wheezy.
The older version of this command has fewer fields.

snippet of older output:
  LV Name                /dev/vg/var
  VG Name                vg

snippit of newer output:
  LV Path                /dev/vg/var
  LV Name                var
  VG Name                vg


They've added a field, and changed what is contained in the old named field.

I've filed a bug with liblinux-lvm-perl about the fact that they don't
pass on LV Path.

Even after fixing the problem with liblinux-lvm-perl, setup-storage has
problems with wipefs.

In my case I error out with:
Executing: wipefs -a vg/fscache
...
wipefs: error: vg/fscache: probing initialization failed

I don't see how that code ever could have worked because I don't think
that $vg/$lv could ever be a valid path for the wipefs command.  This is
clearly what the code is trying to do.

Since the fai-setup-storage code appears to be in a bit of trouble
(somebody made a bunch of commits back in 2011 and hasn't been back to
clean it up), I have managed to kludge 3.4.8 fai-setup-storage to work
with the 4.0.6 fai packages for my local needs.

I've recommended the following on the fai-users mailing list:

1. liblinux-lvm-perl be changed to pass the new LV Path field.
2. downgrade fai-setup-storage back to a known working version (3.4.8?)
3. fix the logic in fai-setup-storage to deal with the multiple fields
for the LV in the manner described by Thomas Neumann on the fai-users
mailing list.

I'm not sure how the Debian package should go forward, but I wanted to
make you aware of the problem.

Let me know if I can provide further information.

-Ken Hahn


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to