From: Sven Eschenberg <sven@eschenberg.eu>
To: "linux-lvm@redhat.com" <linux-lvm@redhat.com>
Subject: [linux-lvm] Problem activating lvm-raid
Date: Fri, 31 Aug 2018 18:28:58 +0200 [thread overview]
Message-ID: <427783b3-1ad1-7411-bfdc-b7054edac4b1@eschenberg.eu> (raw)
Hi all,
I recently had to reboot one of my machines which is usually up 24/7. To
my surprise the activation of the lvm-raid volume failed. I am kinda
stuck finding the reason - the userland got updated regularly and
everything used to work as expected.
Version of lvm being used: lvm2-2.02.181
lvchange -v -ay TsR1/port
Activating logical volume TsR1/port exclusively.
activation/volume_list configuration setting not defined: Checking
only host tags for TsR1/port.
Creating TsR1-port_rmeta_0
Loading table for TsR1-port_rmeta_0 (253:0).
Resuming TsR1-port_rmeta_0 (253:0).
Creating TsR1-port_rimage_0
Loading table for TsR1-port_rimage_0 (253:1).
Resuming TsR1-port_rimage_0 (253:1).
Creating TsR1-port_rmeta_1
Loading table for TsR1-port_rmeta_1 (253:2).
Resuming TsR1-port_rmeta_1 (253:2).
Creating TsR1-port_rimage_1
Loading table for TsR1-port_rimage_1 (253:3).
Resuming TsR1-port_rimage_1 (253:3).
Creating TsR1-port
Loading table for TsR1-port (253:5).
device-mapper: reload ioctl on (253:5) failed: Invalid argument
Removing TsR1-port (253:5)
dmsetup table:
TsR1-port_rmeta_1: 0 512 linear 8:50 512
TsR1-port_rmeta_0: 0 512 linear 8:34 512
TsR1-port_rimage_1: 0 8388608 linear 8:50 1024
TsR1-port_rimage_0: 0 8388608 linear 8:34 1024
Running lvchange again:
lvchange -v -ay TsR1/port
Activating logical volume TsR1/port exclusively.
Activation of logical volume TsR1/port is prohibited while logical
volume TsR1/port_rimage_0 is active.
Since activation fails, shouldn't the changes done not be rolled back
entirely? Usually one would expect identical behavior on a second
invocation.
And thje master question: Why does the activation fail in the first place?
reply other threads:[~2018-08-31 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=427783b3-1ad1-7411-bfdc-b7054edac4b1@eschenberg.eu \
--to=sven@eschenberg.eu \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).