Re: [linux-lvm] What to do about new lvm messages

2020-08-22 Thread Stuart D Gathman

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.

___
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/



[linux-lvm] What to do about new lvm messages

2020-08-22 Thread L A Walsh
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!

___
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/