On Wed, Mar 09, 2016 at 02:47:40PM +0100, J. Roeleveld wrote: > > I’ve never used LVM before, it’s only installed as a dependency for various > > FS tools. Hence, my LVM install is basically pure vanilla. But when I try to > > follow those articles, I get: > > > > kern $ cryptsetup status /dev/mapper/tp > > /dev/mapper/tp is active. > > [...] > > > > kern $ pvcreate /dev/mapper/tp > > /run/lvm/lvmetad.socket: connect failed: No such file or directory > > WARNING: Failed to connect to lvmetad. Falling back to internal scanning. > > Device /dev/mapper/tp not found (or ignored by filtering). > > > > The filter rule in /etc/lvm/lvm.conf simply says the default: > > filter = [ "r|/dev/nbd.*|", "a/.*/" ] > > Meaning ‘include everything except /dev/nbd*’. > > This is the only filter-line in that file?
Yup. I also tried commenting it out, because the in-file docs say that having no filter at all means “accept everything”. > What do you get when running: > pvcreate -vv /dev/mapper/tp > ? Well, running out of patience, I took the SSD to work today and set it up there on an Ubuntu machine. *g* Afterwards I could access LVM info from within a virtual Gentoo system (didn’t try that beforehand). And now I’m back home and pvdisplay on my PC shows me appropriate information. I also just ran pvcreate -ff on my LUKS container with no problem. *shrug* -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me with any social network. When a woman isn’t talking, one should not interrupt her. – Clint Eastwood.
signature.asc
Description: Digital signature
