[gentoo-user] More lvm2 questions

[gentoo-user] More lvm2 questions

[walt]

Something in today's update for ~amd64 changed the bootup behavior
of lvm (again).  Now I get an error message that none of the labels
on my lvm disks can be found (I mount by disk label in fstab).

So now lvm is starting even later than before.  I still get the
(now familiar) error from lvm that file locking failed, but I've
been seeing that since the last thread on the subject and this
problem just started today.  (lvm does start eventually, but only
after fstab fails to find the lvm disks).

While poking around in the rc scripts I realized that device-mapper
daemon is no longer running -- I think it was running a few months
ago but I can't be certain now.  Should it be running?

I added device-mapper to the boot runlevel but it changed nothing
AFAICT.

Also, I notice that a /run directory on tmpfs appeared a while ago
(can't remember when) and I think that should have fixed the file
locking error from lvm, no?  But it's not fixed for me.

What are you guys seeing?  

Re: [gentoo-user] More lvm2 questions

[Dale]

walt wrote:
> Something in today's update for ~amd64 changed the bootup behavior
> of lvm (again).  Now I get an error message that none of the labels
> on my lvm disks can be found (I mount by disk label in fstab).
> 
> So now lvm is starting even later than before.  I still get the
> (now familiar) error from lvm that file locking failed, but I've
> been seeing that since the last thread on the subject and this
> problem just started today.  (lvm does start eventually, but only
> after fstab fails to find the lvm disks).
> 
> While poking around in the rc scripts I realized that device-mapper
> daemon is no longer running -- I think it was running a few months
> ago but I can't be certain now.  Should it be running?
> 
> I added device-mapper to the boot runlevel but it changed nothing
> AFAICT.
> 
> Also, I notice that a /run directory on tmpfs appeared a while ago
> (can't remember when) and I think that should have fixed the file
> locking error from lvm, no?  But it's not fixed for me.
> 
> What are you guys seeing?  
> 
> 
> 


Have you searched the forums?  I'm not sure but I think I ran across
that issue while searching for the other issues you described, missing
lock file.  There was a fix for what you are having but I can't recall
what it was off the top of my head.  I think it was putting
device-mapper in the boot runlevel but don't break things on my bad
memory.  :/

I'm also pretty sure I was using google to search the forums too.  I
have found that google does a MUCH better job with searches than the
forums search tool.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] More lvm2 questions

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 602 bytes --]

On Sun, 29 Apr 2012 14:53:57 -0700, walt wrote:

> Also, I notice that a /run directory on tmpfs appeared a while ago
> (can't remember when) and I think that should have fixed the file
> locking error from lvm, no?  But it's not fixed for me.

AFAIK the default lvm.conf still uses /var/run for locking_dir, /run on
tmpfs is only half the solution, changing the config is the other half.

I've rebooted several times today, trying to fix a separate problem, and
haven't had any problems with lvm.


-- 
Neil Bothwick

Memory Map - A sheet of paper showing location of computer store.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Re: More lvm2 questions

[walt]

On 04/29/2012 03:57 PM, Neil Bothwick wrote:
> On Sun, 29 Apr 2012 14:53:57 -0700, walt wrote:
> 
>> Also, I notice that a /run directory on tmpfs appeared a while ago
>> (can't remember when) and I think that should have fixed the file
>> locking error from lvm, no?  But it's not fixed for me.
> 
> AFAIK the default lvm.conf still uses /var/run for locking_dir, /run on
> tmpfs is only half the solution, changing the config is the other half.

Correct, thanks!  *Now* I remember reading that part of the thread :(

The reason this problem came up just today, I discovered, is that late
yesterday afternoon I was adding libreoffice 3.5.* to package.mask and
noticed that lvm2 was listed there.  I couldn't remember why I'd added
lvm2 to the list so I commented it out.  Thanks to you I remember why
I did, and the problem is now fixed :)

(Thanks also to Dale.  Hope you're feeling better.)

Re: [gentoo-user] Re: More lvm2 questions

[Dale]

walt wrote:

> 
> (Thanks also to Dale.  Hope you're feeling better.)
> 

I knew I read about this somewhere but couldn't recall what the fix was.
 I thought it was on the forums since I do search there before asking
here, most of the time anyway.

What version are you on when this happened?  Also, what version did you
go back to?  I ask because I have not masked any version here.  I may
need to do that since I have all but /boot and / on LVM now.

Also, after my recent move, I see now I should have made / MUCH smaller.
 I mean MUCH MUCH smaller.  :/  There goes that hindsight again.
Naturally it is NOT on LVM.

I'm sort of getting used to being less than 100%.  Actually, less than
50% most days.  ;-)

Dale

:-)  :-)


-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Re: More lvm2 questions

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 427 bytes --]

On Sun, 29 Apr 2012 20:05:00 -0500, Dale wrote:

> Also, after my recent move, I see now I should have made / MUCH smaller.
>  I mean MUCH MUCH smaller.  :/  There goes that hindsight again.

Yes, I usually make / about 400MB and it is half full.

> Naturally it is NOT on LVM.

If you're using in "init thingy" [tm] you may as well put / on an LV too.


-- 
Neil Bothwick

Top Oxymorons Number 31: Small crowd

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: More lvm2 questions

[Dale]

Neil Bothwick wrote:
> On Sun, 29 Apr 2012 20:05:00 -0500, Dale wrote:
> 
>> Also, after my recent move, I see now I should have made / MUCH smaller.
>>  I mean MUCH MUCH smaller.  :/  There goes that hindsight again.
> 
> Yes, I usually make / about 400MB and it is half full.

Mines bigger than yours:

Filesystem              Size  Used Avail Use% Mounted on
rootfs                   24G  1.3G   21G   6% /

ROFL


> 
>> Naturally it is NOT on LVM.
> 
> If you're using in "init thingy" [tm] you may as well put / on an LV too.
> 
> 


Well, I may later on do just that.  If / was on LVM, I could shrink that
puppy pretty easy.  Look at all that wasted space.  Grrrrr.  I started
to make it 10G but couldn't recall what I had calculated and I couldn't
find where I wrote it down either.

My only gripe, gkrellm can't see the LVM groups and such.  It's sees the
partition but just as one thing to monitor and not separate as they
actually are for the file systems.  Oh well, my Cooler Master HAF-932
case has that nice BRIGHT blue light.  If it is on, it's doing
something.  :/

Oh, been saving money for that nice LARGE drive too.  Maybe in a couple
months I can get me a 2 or 3Tb drive.  Yeppie!!

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

[gentoo-user] Re: More lvm2 questions

[walt]

On 04/29/2012 06:05 PM, Dale wrote:


> What version are you on when this happened?  Also, what version did you
> go back to?  I ask because I have not masked any version here.  I may
> need to do that since I have all but /boot and / on LVM now.

I'm now running lvm2-2.02.95-r1 on both ~amd64 machines and all is well.
The secret, as Neil reminded us, is to change /etc/lvm/lvm.conf to read:

locking_dir = "/run/lock/lvm"

This works because /run (recently, anyway) is created/mounted on tmpfs
before lvm starts, and that gives lvm somewhere to write its lock file
when it starts.  The default setting is /dev/.lvm, but /dev may not
exist when lvm needs to start, depending on how your machine is set up,
I think/guess.

This applies only to ~ versions, BTW, not stable.