Quoting Andrei Borzenkov <arvidjaar@gmail.com>:
23.08.2015 04:07, Neil Rickert ?????:
That's the way it should be.
Not really. If lvmetad is enabled, volumes should be auto-activated by default (there is lvm.conf setting to only limit auto-activation to list of specific volumes). But it had been flipped on and off due to various problems and I believe the latest state is lvmetad is disabled, which means manual activation is required.
I guess it's more of a flaw in LVM; the vgchange command is not exactly at the top of the list when you start looking. Also, when you use this software you don't know that it is a /volume group/ that you need to activate; as a user, you just think "lvm!". I even remember reading about vgchange -ay in the manual of LVM, but it was a while back (like 6 months ago). I had forgotten. When you start lvm lvm> help It lists vgchange as "Change volume group attributes" -- not something you think of "hey, that is going to activate my volumes!" There is absolutely no indication WHATSOEVER as to what you need to use :-/. There is also no man pages when you are in a rescue system. The only thing that could indicate what you need to do, would be: lvm> help vgchange The funny thing, of course, or the irony, is that in order to use the rescue system, you must have access to your system so you can go on the web. ;-).
The "cryptsetup" command is for encryption. Maybe I am opening the encrytped container because I want to reformat, and destroy the LVM. The "cryptsetup" command cannot guess that.
Well, you have a point. That means you'd want to reformat the container while it is mapped. But it's not hard (pretty obvious) how you can remove the VG and the PV. After that I believe formatting it would be possible in any case?. There would be no mapping left and hence you could access the crypt device without a problem. So from a user point of view that use case is not hard to achieve even when the LVM gets auto-mapped.
If the partition is listed in "/etc/crypttab", then my experience is that the LVM volumes get mapped during boot.
Right. Obviously that wasn't the case in my rescue system ;-).
vgchange -a y [optionally add name of volume group]
Thanks again. I guess.. I had already found it once I had internet access again. Bart. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org