Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-user
Navigation:
Lists: gentoo-user: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-user@g.o
From: Neil Bothwick <neil@...>
Subject: Re: "lvm failed to start"
Date: Sat, 7 Apr 2012 11:38:40 +0100
On Sat, 7 Apr 2012 02:47:41 -0600, Carlos Sura wrote:

> > The problem is that it is trying to write to /var/lock, which is on /
> > at this point, rather than /run/lock, which is on a writeable tmpfs.

> I got this error, and saw a bugfile on Gentoo, just downgrade to your
> previous working version and you will get it working again.

That bug report also showed the correct solution. There's no need to
downgrade, just change the locking_dir location from /var/lock
to /run/lock. Not only is this simpler and faster, it means another
update can't cause the same problem.


-- 
Neil Bothwick

When there's a will, I want to be in it.
Attachment:
signature.asc (PGP signature)
Replies:
Re: "lvm failed to start"
-- Alan McKinnon
References:
"lvm failed to start"
-- walt
Re: "lvm failed to start"
-- Dan Johansson
Re: "lvm failed to start"
-- Neil Bothwick
Re: "lvm failed to start"
-- Dan Johansson
Re: "lvm failed to start"
-- Neil Bothwick
Re: "lvm failed to start"
-- Carlos Sura
Navigation:
Lists: gentoo-user: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: "lvm failed to start"
Next by thread:
Re: "lvm failed to start"
Previous by date:
Re: FFTOOLS flags?
Next by date:
multiple bluetooth devices


Updated May 04, 2012

Summary: Archive of the gentoo-user mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.