Opened 9 years ago

Closed 9 years ago

#6056 closed enhancement (fixed)

LVM2-2.02.115

Reported by: Pierre Labastie Owned by: Pierre Labastie
Priority: normal Milestone: 7.7
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

ftp://sources.redhat.com/pub/lvm2/LVM2.2.02.115.tgz

ftp://sources.redhat.com/pub/lvm2/WHATS_NEW

Version 2.02.115 - 21st January 2015
====================================
  Report segment types without monitoring support as undefined.
  Support lvchange --errorwhenfull for thin pools.
  Improve the processing and reporting of duplicate PVs.
  Report lv_health_status and health attribute also for thin pool.
  Add lv_when_full reporting field.
  Add support for lvcreate --errorwhenfull y|n for thin pools.
  Fix lvconvert --repair to honour resilience requirement for segmented RAID LV.
  Filter out partitioned device-mapper devices as unsuitable for use as PVs.
  Also notify lvmetad about filtered device if using pvscan --cache DevicePath.
  Use LVM's own selection instead of awk expressions in clvmd startup scripts.
  Do not filter out snapshot origin LVs as unusable devices for an LVM stack.
  Fix incorrect rimage names when converting from mirror to raid1 LV (2.02.112).
  Introduce pvremove_many to avoid excessive metadata re-reading and messages.
  Check for cmirror availability during cluster mirror creation and activation.
  Add cache_policy and cache_settings reporting fields.
  Add missing recognition for --binary option with {pv,vg,lv}display -C.
  Fix vgimportclone to notify lvmetad about changes done if lvmetad is used.
  Fix vgimportclone to properly override config if it is missing in lvm.conf.
  Fix automatic use of configure --enable-udev-systemd-background-jobs.
  Correctly rename active split LV with -splitmirrors for raid1.
  Add report/compact_output to lvm.conf to enable/disable compact report output.
  Still restrict mirror region size to power of 2 when VG extent size is not.

ftp://sources.redhat.com/pub/lvm2/WHATS_NEW_DM

Version 1.02.93 - 21st January 2015
===================================
  Reduce severity of ioctl error message when dmeventd waitevent is interrupted.
  Report 'unknown version' when incompatible version numbers were not obtained.
  Report more info from thin pool status (out of data, metadata-ro, fail).
  Support error_if_no_space for thin pool target.
  Fix segfault while using selection with regex and unbuffered reporting.
  Add dm_report_compact_fields to remove empty fields from report output.
  Remove unimplemented dm_report_set_output_selection from libdevmapper.h.

Change History (10)

comment:1 by Pierre Labastie, 9 years ago

Owner: changed from blfs-book@… to Pierre Labastie
Status: newassigned

comment:2 by Pierre Labastie, 9 years ago

I am having trouble with tests. One first test reports:

-- Timed out normal:shell/lvconvert-raid.sh (end) ---
Running normal:shell/lvconvert-repair-dmeventd.sh

Then all tests time out (and it looks like that even the host "lvm", tried in another wondow, does not work anymore). Hter is an overall time out of 5 h or so for the tests, so that eventually, the tests end. But the system is left into a weird state (when shutting down, the system cannot umount /, "system is busy",but nothing is reported by "mount").

Problem is: at least 3 packages are involved: kernel, udev, and lvm itself. What to check first, I do not know...

comment:3 by Pierre Labastie, 9 years ago

I forgot to says that I have kernel 3.18.2.

Downgrading to LVM2-2.02.114 still gives the same behavior.

But bingo! Downgrading kernel to 3.17.4 allows the tests to run to completion. Trying again with 2.02.115 and kernel 3.17.4.

Last edited 9 years ago by Pierre Labastie (previous) (diff)

comment:4 by Pierre Labastie, 9 years ago

Version 2.02.115 + kernel 3.17.4: allows also the tests to run to completion. There are 2 failures, 7 warnings, and 37 tests skipped (out of a total of ~200). Also, all 200 "cluster" type tests are skipped, but I guess the reason is just that my VM does not have suitable (emulated) hardware or configuration.

I guess I've gotten to try with latest kernel (3.18.3).

comment:5 by Pierre Labastie, 9 years ago

3.18.3 gives times-out too. Problem is that it is not reproducible: the first timed out test is not always the same!

comment:6 by Pierre Labastie, 9 years ago

Do not know what to do with the book. Should I update (seems that for day to day use, LVM is OK), with a note about the kernel version?

comment:7 by Pierre Labastie, 9 years ago

Looks like kernel 3.18.1 is OK

comment:8 by bdubbs@…, 9 years ago

Intermittent problems are almost always HW related. A short comment about timing issues would be appropriate, but go ahead and update please.

comment:9 by Pierre Labastie, 9 years ago

Well: the tests pass always (well a couple of times for each) with kernel 3.17.4 and 3.18.1. Anyway, will update (tomorrow, it is getting late here).

comment:10 by Pierre Labastie, 9 years ago

Resolution: fixed
Status: assignedclosed

fixed at r15383 and r15384

Note: See TracTickets for help on using tickets.