archive mirror
 help / color / mirror / Atom feed
From: Stuart D Gathman <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] What to do about new lvm messages
Date: Sat, 22 Aug 2020 07:45:24 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, 22 Aug 2020, L A Walsh wrote:

> I am trying to create a new pv/vg/+lvs setup but am getting some weird messages
> pvcreate  -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.
>  Physical volume "/dev/sda1" successfully created.
> So why am I getting a message about not clearing a hint file (running s root)

Because there is an ole PV header on sdd1

>> 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

You wrote a new PV header on sda1 - but that didn't do diddly squat 
about the old one on sdd1.

> the VG to update.
>  Cannot access VG Space with system ID Ishtar with unknown local system ID.
>  Device /dev/sda1 excluded by a filter.

The PV filter is excluding sda1.  Are you confused about what is on 
which sdx?

> dd if=/dev/zero of=/dev/sda1 bs=4096 count=1
> 1+0 records in
> 1+0 records out
> 4096 bytes (4.1 kB, 4.0 KiB) copied, 0.000175409 s, 23.4 MB/s

I hope sda1 was really what you think it was.

What is on sdd1?  None of your listings examine it.

  reply	other threads:[~2020-08-22 12:39 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 [this message]
2020-08-24  2:35   ` L A Walsh
2020-08-24 15:33 ` David Teigland

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).