archive mirror
 help / color / mirror / Atom feed
From: David Teigland <>
To: L A Walsh <>
Subject: Re: [linux-lvm] What to do about new lvm messages
Date: Mon, 24 Aug 2020 10:33:25 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Aug 22, 2020 at 04:36:27AM -0700, L A Walsh wrote:
> pvcreate  -M2 --pvmetadatacopies 2 /dev/sda1
>   Failed to clear hint file.
> So why am I getting a message about not clearing a hint file (running s root)

I'm guessing that no commands have permission to use /run/lvm/hints, so
they just skip it.  But, this is one place printing a warning about it.
I'll remove the warning.  Run 'pvs', and check if /run/lvm/hints exists.
If not, you might want to look at permission issues.

> and how do I modify a VG that I don't want to make any modifications to?

To fix that header you can run 'vgck --updatemetadata Backup'.

> From an online man page, I should have been able to use -ff to recreate
> a pv over the top of a preexisting one, but that didn't seem to work.  I
> got:
>  pvcreate -ff -M2 --pvmetadatacopies 2 /dev/sda1
>   Failed to clear hint file.
>   WARNING: PV /dev/sdd1 in VG Backup is using an old PV header, modify
> the VG to update.
>   Cannot access VG Space with system ID Ishtar with unknown local system ID.
>   Device /dev/sda1 excluded by a filter.

You're not using system ID correctly.

> I also ran into a problem on how to tell vgcreate to use the whole pv.
> That was complicated by trying to specify my hostname as a system id:

>   Cannot access VG Space with system ID Ishtar with unknown local system ID.

The machine needs to have a system ID configured.  See lvmsysystemid(7)
and edit lvm.conf/lvmlocal.conf.  Then vgcreate will use the machine's
system for the new VG.  Using --systemid overrides the local value which
you don't want.

      parent reply	other threads:[~2020-08-24 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22 11:36 L A Walsh
2020-08-22 11:45 ` Stuart D Gathman
2020-08-24  2:35   ` L A Walsh
2020-08-24 15:33 ` David Teigland [this message]

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:

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

  git send-email \ \ \ \ \
    --subject='Re: [linux-lvm] What to do about new lvm messages' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).