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