Could not successfully backup ‘blah.tld’: Failed to backup LVM/MD configuration

So – today’s issue for R1soft is that it is presenting a subtly different error for a number of hosts. They are indeed all CentOS hosts, and all appear to be backing up – however, they are marked as fail and announced “Could not successfully backup ‘blah.tld’: Failed to backup LVM/MD configuration“. R1soft LVM centos fail.

While the data may be there – clearly the chances of a BMR are slim to flipping none. Nice.

So – I raised it and they responded with the following link:

http://repo.r1soft.com/modules/RHEL_7.4_x64/RHEL_7.4_lvm_issue.txt

Not so much a wiki article but a file kicking around within the modules directory – here is what is has to say:

 

Older LVM code does not play well with the very latest LVM2 configs inside RHEL 7.4

####################################################################

If you use the configuration file from lvm2 >= 2.02.171 with any earlier lvm,
all lvm utilities break with the error:

Invalid units specification

This happens because lvm.conf contains a new value: ( Used to default to “h” )

# Default value for –units argument.
units = “r”

The problem is that older version of LVM do not understand this
and fail with this error message:

Invalid units specification

###################################################################

METHOD #1
The lvm.conf gets loaded into memory at initialization time.
Editing the file does not change the behavior. A reboot is required
Commenting or editing that one line and rebooting resolves the issue.

METHOD #2
Replacing our static binary with the new OS version in 7.4
a.) mv /usr/sbin/r1soft/lib/lvm.static /usr/sbin/r1soft/lib/lvm.static.old
b.) ln -s /sbin/lvm /usr/sbin/r1soft/lib/lvm.static

Now it transpires that we have run into this in the past, however, I have not. We went with METHOD #1 here, and it transpires if you leave it a couple of hours you do not require to reboot either in the previous cases.

So – here we are in /etc/lvm/lvm.conf

# Configuration section global.
# Miscellaneous global LVM settings.
global {
# Configuration option global/umask.
# The file creation mask for any files and directories created.
# Interpreted as octal if the first digit is zero.
umask = 077
# Configuration option global/test.
# No on-disk metadata changes will be made in test mode.
# Equivalent to having the -t option on every command.
test = 0
# Configuration option global/units.
# Default value for --units argument.
units = "r"

However – what it apparently needs to say is the following:

# Configuration section global.
# Miscellaneous global LVM settings.
global {
# Configuration option global/umask.
# The file creation mask for any files and directories created.
# Interpreted as octal if the first digit is zero.
umask = 077
# Configuration option global/test.
# No on-disk metadata changes will be made in test mode.
# Equivalent to having the -t option on every command.
test = 0
# Configuration option global/units.
# Default value for --units argument.
units = "h"

 

<rant>While it is great to have a fix, and have that sent over in a timely manner from support – it is not great that it would appear their code is not being developed. Sure, the interface keeps showing, and in some ways now does what is expected / consistent / doesn’t generate rogue tasks on its own … however really? Seriously? It is a shame that this is currently the best of a bad lot. </rant>

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this:
Skip to toolbar