public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Thorne <lexiconifernelius@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] lvmetad Errors
Date: Sun, 5 Jul 2015 18:01:37 +0100	[thread overview]
Message-ID: <CAB5mfck-uUxONVwa=J8AYRzp6K5o6rc7jEiHj9MT9xyy3zBGCg@mail.gmail.com> (raw)
In-Reply-To: <1476249.0FqsB4fzEI@wstn>

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

Unfortunately dmraid is not in any runlevel. I think it is lvm that's
starting lvmetad despite use_lvmetad=0 being set in the configuration file.
Unfortunately I think I'm just going to have to learn to live with the
error message.

Thanks,
Alex

On 25 June 2015 at 10:19, Peter Humphrey <peter@prh.myzen.co.uk> wrote:

> On Wednesday 24 Jun 2015 12:13:06 Alex Thorne wrote:
>
> > I used to get the following error in /var/log/rc.log
> >     /run/lvm/lvmetad.socket: connect failed: No such file or directory
> > I am not sure why this was happening, but I read that one fix was to
> > disable lvmetad entirely. And so I set
> >    use_lvmetad = 0
> > in /etc/lvm/lvm.conf.
> >
> > However, now I get error messages of the following form (e.g. when
> running
> > grub2-mkconfig):
> >   WARNING: lvmetad is runing but disabled. Restart lvmetad before
> enabling
> > it!
>
> I don't have an rc.log but I used to see this scroll by during boot and
> shutdown. The cure seems to be to remove mdraid from the boot run-level
> [1].
>
> I don't properly understand what's going on here: I needed mdraid in boot
> while building the system, but once it was up and running and udev was
> starting the RAID volumes it was better to remove it. I still have
> use_lvmetad
> = 1. Bug 521280 refers.
>
> > I ran
> >    /etc/init.d/lvmetad needsme
> > and got
> >    lvm-monitor lvm
> > I don't understand why lvm is starting lvmetad even when I have disabled
> > it. lvmetad is certainly not in any runlevel itself and I just don't know
> > where to go from here.
> >
> > I would appreciate some advice on how to fix either problem (the socket
> > connect issue when lvmetad is enabled, or the fact that lvmetad still
> > starts when it's disabled...)
>
> [1]     ...and have a rescue system ready to chroot from and put it back
> :-)
>
> --
> Rgds
> Peter
>
>
>

[-- Attachment #2: Type: text/html, Size: 2511 bytes --]

  reply	other threads:[~2015-07-05 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 11:13 [gentoo-user] lvmetad Errors Alex Thorne
2015-06-25  9:19 ` Peter Humphrey
2015-07-05 17:01   ` Alex Thorne [this message]
2015-07-06  7:54     ` Peter Humphrey
2015-07-06  9:19       ` Alex Thorne
2015-07-06 15:01         ` Peter Humphrey
2015-07-12 18:51           ` Alex Thorne
2015-07-12 19:25             ` Alan McKinnon
2015-07-12 20:46               ` Daniel Frey
2015-07-12 20:51                 ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAB5mfck-uUxONVwa=J8AYRzp6K5o6rc7jEiHj9MT9xyy3zBGCg@mail.gmail.com' \
    --to=lexiconifernelius@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox