linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: L A Walsh <lvm@tlinx.org>
To: linux-lvm@redhat.com
Subject: [linux-lvm] What to do about new lvm messages
Date: Sat, 22 Aug 2020 04:36:27 -0700	[thread overview]
Message-ID: <CALOnQv5via9sF2FP81uGXe+CzLqX0it7T0NvRSVxV8TBbhUuvg@mail.gmail.com> (raw)

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)

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

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.
---
   So it seems that is broken.  I was able to work around that with:
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 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:
vgcreate -A y --alloc contiguous --systemid Ishtar --dataalignment
64KiB Space /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.
  Volume group "Space" successfully created with system ID Ishtar

vgs
  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.
  VG     #PV #LV #SN Attr   VSize  VFree
Didn't know where the VG group ended up, which was why I needed to
redo creating the pv (vgremove didn't work):
vgremove Space
  Failed to clear hint file.
  Cannot access VG Space with system ID Ishtar with unknown local system ID.
  Cannot access VG Space with system ID Ishtar with unknown local system ID.

Version info:
pvcreate --version
  LVM version:     2.03.05(2) (2019-06-15)
  Library version: 1.03.01 (2019-06-15)
  Driver version:  4.42.0
  Configuration:   ./configure --host=x86_64-suse-linux-gnu
--build=x86_64-suse-linux-gnu --program-prefix=
--disable-dependency-tracking --prefix=/usr --exec-prefix=/usr
--bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64
--libexecdir=/usr/lib --localstatedir=/var --sharedstatedir=/var/lib
--mandir=/usr/share/man --infodir=/usr/share/info
--disable-dependency-tracking --enable-dmeventd --enable-cmdlib
--enable-udev_rules --enable-udev_sync --with-udev-prefix=/usr/
--enable-selinux --enable-pkgconfig --with-usrlibdir=/usr/lib64
--with-usrsbindir=/usr/sbin --with-default-dm-run-dir=/run
--with-tmpfilesdir=/usr/lib/tmpfiles.d --with-thin=internal
--with-device-gid=6 --with-device-mode=0640 --with-device-uid=0
--with-dmeventd-path=/usr/sbin/dmeventd
--with-thin-check=/usr/sbin/thin_check
--with-thin-dump=/usr/sbin/thin_dump
--with-thin-repair=/usr/sbin/thin_repair --enable-blkid_wiping
--enable-lvmpolld --enable-realtime --with-cache=internal
--with-default-locking-dir=/run/lock/lvm --with-default-pid-dir=/run
--with-default-run-dir=/run/lvm --enable-cmirrord --enable-fsadm
--disable-silent-rules --enable-write_install --with-vdo=internal
--with-vdo-format=/usr/bin/vdoformat

Anyway -- why does it keep failing to clear the hint file?  And how
can I modify a VG without changing it (just to remove the annoying
WARNING with every command).

Thanks!

             reply	other threads:[~2020-08-22 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22 11:36 L A Walsh [this message]
2020-08-22 11:45 ` Stuart D Gathman
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:
  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=CALOnQv5via9sF2FP81uGXe+CzLqX0it7T0NvRSVxV8TBbhUuvg@mail.gmail.com \
    --to=lvm@tlinx.org \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] What to do about new lvm messages' \
    /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

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