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