[Rear-users] Recover using Centos 6
dag at wieers.com
Mon Sep 19 20:23:42 CEST 2011
On Mon, 19 Sep 2011, Jeroen Hoekx wrote:
> On 19 September 2011 14:19, Frank Slotta <f_slotta at gmx.de> wrote:
>> [test at slotest ~]$ rpm -qa | grep lvm
> This is not nice :-(
>> From the LVM changelog:
> Version 2.02.73 - 18th August 2010
> Add --norestorefile option to pvcreate.
> Require --restorefile when using pvcreate --uuid.
> That's how it's implemented in Rear.
> Yet, CentOS and RHEL 6 are using 2.02.72 with some additional patches.
> One of their patches adds the restorefile functionality.
> Suggestions from anyone on how to handle this in a clean way?
> Anyone aware of one of the distributions shipping unpatched 2.02.72? I
> don't have my VMs nearby to test.
This might not be such a big deal afterall, on an updated RHEL 6.1:
* Fri Jun 17 2011 Milan Broz <mbroz at redhat.com> - 2.02.84-6
- Fix repair of mirror volume after transient device error.
* Sat Jun 11 2011 Milan Broz <mbroz at redhat.com> - 2.02.84-5
- Fix reduction of mirrors with striped segments.
But CentOS 6.0 ships with 2.02.72-8.el6 and currently updates to
2.02.72-8.el6_0.4. However, Red Hat provides an SRPM 2.02.83-3.el6 from
ftp.redhat.com (likely this is RHEL 6.1 vanilla).
What is weird from the RHEL6 lvm2 RPM changelog, they don't even mention
release 2.02.72-8.el6_0.4 in that changelog:
* Sat Oct 16 2010 Milan Broz <mbroz at redhat.com> - 2.02.74-1
- Convey need for snapshot-merge target in lvconvert error message.
- Give correct error message when creating a too-small snapshot.
- Implement vgextend --restoremissing.
- Fix --force and --yes flags in lvconvert.
- Fix possible data corruption when using fsadm and resizing device.
- Allow to set limit for repeated access to broken devices.
- Fix hang when repairing a mirrored-log that had both devs fail.
Resolves: #638283 #587063 #537913 #252420 #642055 #643365
* Tue Aug 31 2010 Milan Broz <mbroz at redhat.com> - 2.02.73-2
- Fix clustered mirror log daemon detection.
* Thu Aug 26 2010 Milan Broz <mbroz at redhat.com> - 2.02.73-1
- Update to latest upstream release, all fixes and enhancements
detailed in WHATS_NEW file.
- CVE-2010-2526: Fix insecurity when communicating between lvm2 and clvmd.
Resolves: #627541 #589805 #474914 #585328 #588441 #568138
Resolves: #232499 #235095 #547895 #616150 #486994 #560105
Resolves: #560111 #590017 #549174 #559351 #582330 #627701
Resolves: #564516 #617972 #552721 #592428
* Tue Jun 08 2010 Milan Broz <mbroz at redhat.com> - 2.02.56-12
- Fix initialisation of logging to file to not cause boot failure.
- Fix lvchange --refresh to require partial flag if PVs are missing.
Resolves: #592967 #598886
So I assume that these updates have happened after RHEL6.1 Beta was
already being produced. Which in itself is weird. It would be nice to know
what the changelog of the RPM says about the 2.02.72 series.
Also no mentions of --norestorefile or --uuid throughout the changelog or
technical notes, so it might be one of the Rhbz article references :-/
The RHEL 6.1 technical notes about lvm2 are located here:
Reading the technical notes, I would be scared using anything older than
RHEL6.1, but that's probably my nature ;-)
-- dag wieers, dag at wieers.com, http://dag.wieers.com/
-- dagit linux solutions, info at dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
More information about the rear-users