linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
* [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180
@ 2020-09-10 13:53 KrishnaMurali Chennuboina
  2020-09-14 14:58 ` Roger Heflin
  0 siblings, 1 reply; 8+ messages in thread
From: KrishnaMurali Chennuboina @ 2020-09-10 13:53 UTC (permalink / raw)
  To: LVM general discussion and development


[-- Attachment #1.1: Type: text/plain, Size: 926 bytes --]

Hi Team,

While trying to analyze one the issue, we felt that upgrading the current
LVM2 package in our repository will be the best approach.
As part of that, we have updated the respective package from  2.02.176 to
2.02.180. We have verified the same and booted x86_64 hardware without any
issues.

But while trying to boot mips64 hardware we have started observing the
below issue.  Providing the snippet of the log,

# executing command: vgchange -an
(status, output): (0,   WARNING: Failed to connect to lvmetad. Falling back
to device scanning.)
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Attached the detailed log for reference. There is no other change included
other than the LVM2 update.

LVM2 Version: 2.02.176
Updated LVM2 version: 2.02.180

Please share inputs on why this issue is being observed with .180 version?
Please let me know if i can share any other information.

Thanks.

[-- Attachment #1.2: Type: text/html, Size: 1182 bytes --]

[-- Attachment #2: lvm_bootupIssue.txt --]
[-- Type: text/plain, Size: 6076 bytes --]

2020-09-09 15:00:19,306 DEBUG - storageconfig.load_drbd_kernel_module - Looking for FSHWDRBD entries from LDAP.
2020-09-09 15:00:19,307 DEBUG - storageconfig.load_drbd_kernel_module - ldapsearch result: [].
2020-09-09 15:00:30,467 DEBUG - funclib.execute - <command="/bin/fssrcli -ifvm --fast-drbd-sync", round=1, ret=1>
# executing command: vgchange -an 
(status, output): (0,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.)
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
initializing disk "/dev/sda" on node "CFPU-0" by wiping the disk
# executing command: pvs -o pv_name --noheadings 2>/dev/null
(status, output): (0, )

# executing command: rm -rf /etc/lvm/backup
(status, output): (0, )

# executing command: rm -rf /etc/lvm/archive
(status, output): (0, )

# executing command: dd if=/dev/zero bs=512 count=4 of=/dev/sda1
(status, output): (0, 4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00194421 s, 1.1 MB/s)
4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00194421 s, 1.1 MB/s
# executing command: dd if=/dev/zero bs=512 count=4 of=/dev/sda2
(status, output): (0, 4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.0114675 s, 179 kB/s)
4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.0114675 s, 179 kB/s
# executing command: dd if=/dev/zero bs=512 count=4 of=/dev/sda3
(status, output): (0, 4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00637096 s, 321 kB/s)
4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00637096 s, 321 kB/s
# executing command: dd if=/dev/zero bs=512 count=4 of=/dev/sda
(status, output): (0, 4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00820429 s, 250 kB/s)
4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00820429 s, 250 kB/s
# executing command: create_partition /dev/sda1 500M 83 true
(status, output): (0, INFO: erasing partition table on device /dev/sda)
INFO: erasing partition table on device /dev/sda
# executing command: create_partition /dev/sda2 500M 83 false
(status, output): (0, blockdev: ioctl error on BLKRRPART: Device or resource busy)
blockdev: ioctl error on BLKRRPART: Device or resource busy
# executing command: create_partition /dev/sda3 -1M 8e false
(status, output): (0, blockdev: ioctl error on BLKRRPART: Device or resource busy)
blockdev: ioctl error on BLKRRPART: Device or resource busy
# executing command: pvs -o pv_name --noheadings 2>/dev/null
(status, output): (0, )

# executing command: rm -rf /etc/lvm/backup
(status, output): (0, )

# executing command: rm -rf /etc/lvm/archive
(status, output): (0, )

# executing command: dd if=/dev/zero bs=512 count=4 of=/dev/sda1
(status, output): (0, 4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.0032232 s, 635 kB/s)
4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.0032232 s, 635 kB/s
# executing command: dd if=/dev/zero bs=512 count=4 of=/dev/sda2
(status, output): (0, 4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00522931 s, 392 kB/s)
4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00522931 s, 392 kB/s
# executing command: dd if=/dev/zero bs=512 count=4 of=/dev/sda3
(status, output): (0, 4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.0123737 s, 166 kB/s)
4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.0123737 s, 166 kB/s
# executing command: dd if=/dev/zero bs=512 count=4 of=/dev/sda
(status, output): (0, 4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00804545 s, 255 kB/s)
4+0 records in
4+0 records out
2048 bytes (2.0 kB, 2.0 KiB) copied, 0.00804545 s, 255 kB/s
# executing command: create_partition /dev/sda1 500M 83 true
(status, output): (0, INFO: erasing partition table on device /dev/sda)
INFO: erasing partition table on device /dev/sda
# executing command: create_partition /dev/sda2 500M 83 false
(status, output): (0, blockdev: ioctl error on BLKRRPART: Device or resource busy)
blockdev: ioctl error on BLKRRPART: Device or resource busy
# executing command: create_partition /dev/sda3 -1M 8e false
(status, output): (0, blockdev: ioctl error on BLKRRPART: Device or resource busy)
blockdev: ioctl error on BLKRRPART: Device or resource busy
# executing command: vgchange -ay 
(status, output): (0,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.)
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
# executing command: pvcreate -ffy /dev/sda3
(status, output): (5,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Error reading device /dev/sda3 at 0 length 4096.
  Error reading device /dev/ram0 at 0 length 4096.
  Error reading device /dev/loop0 at 0 length 4096.
  Error reading device /dev/sda at 0 length 512.
  Error reading device /dev/sda at 0 length 4096.
  Error reading device /dev/ram1 at 0 length 4096.
  Error reading device /dev/sda1 at 0 length 4096.
  Error reading device /dev/ram2 at 0 length 4096.
  Error reading device /dev/sda2 at 0 length 4096.
  Error reading device /dev/ram3 at 0 length 4096.
  Error reading device /dev/ram4 at 0 length 4096.
  Error reading device /dev/ram5 at 0 length 4096.
  Error reading device /dev/ram6 at 0 length 4096.
  Error reading device /dev/ram7 at 0 length 4096.
  Error reading device /dev/ram8 at 0 length 4096.
  Error reading device /dev/ram9 at 0 length 4096.
  Error reading device /dev/ram10 at 0 length 4096.
  Error reading device /dev/ram11 at 0 length 4096.
  Error reading device /dev/ram12 at 0 length 4096.
  Error reading device /dev/ram13 at 0 length 4096.
  Error reading device /dev/ram14 at 0 length 4096.
  Error reading device /dev/ram15 at 0 length 4096.
  Device /dev/sda3 excluded by a filter.)
Failed to execute command: pvcreate -ffy /dev/sda3
ec=0

[-- Attachment #3: lvm_bootupIssue_verbose.txt --]
[-- Type: text/plain, Size: 21756 bytes --]

bash-4.4#
bash-4.4# pvs
  Error reading device /dev/ram0 at 0 length 4096.
  Error reading device /dev/loop0 at 0 length 4096.
  Error reading device /dev/sda at 0 length 512.
  Error reading device /dev/sda at 0 length 4096.
  Error reading device /dev/ram1 at 0 length 4096.
  Error reading device /dev/sda1 at 0 length 4096.
  Error reading device /dev/ram2 at 0 length 4096.
  Error reading device /dev/sda2 at 0 length 4096.
  Error reading device /dev/ram3 at 0 length 4096.
  Error reading device /dev/sda3 at 0 length 4096.
  Error reading device /dev/ram4 at 0 length 4096.
  Error reading device /dev/sda4 at 0 length 4096.
  Error reading device /dev/ram5 at 0 length 4096.
  Error reading device /dev/ram6 at 0 length 4096.
  Error reading device /dev/ram7 at 0 length 4096.
  Error reading device /dev/ram8 at 0 length 4096.
  Error reading device /dev/ram9 at 0 length 4096.
  Error reading device /dev/ram10 at 0 length 4096.
  Error reading device /dev/ram11 at 0 length 4096.
  Error reading device /dev/ram12 at 0 length 4096.
  Error reading device /dev/ram13 at 0 length 4096.
  Error reading device /dev/ram14 at 0 length 4096.
  Error reading device /dev/ram15 at 0 length 4096.
  Error reading device /dev/sdb at 0 length 512.
  Error reading device /dev/sdb at 0 length 4096.
  Error reading device /dev/sdb1 at 0 length 4096.
  Error reading device /dev/sdb2 at 0 length 4096.
  Error reading device /dev/sdb3 at 0 length 4096.
  Read-only locking type set. Write locks are prohibited.
  Recovery of standalone physical volumes failed.
  Cannot process standalone physical volumes
bash-4.4# strace pvcreate -ffy /dev/sda3
execve("/usr/bin/pvcreate", ["pvcreate", "-ffy", "/dev/sda3"], 0xffffa28020 /* 23 vars */) = 0
brk(NULL)                               = 0xaabbe4d000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xfff4190000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/octeon2/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "octeon2/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/tls/octeon2/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/tls/octeon2", 0xffffe28d40)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/tls/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/tls", 0xffffe28d40)          = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/octeon2/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/octeon2", 0xffffe28d40)      = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
mmap(NULL, 64, PROT_READ, MAP_PRIVATE, 3, 0) = 0xfff418f000
close(3)                                = 0
openat(AT_FDCWD, "/lib64/tls/octeon2/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib64/tls/octeon2", 0xffffe28d40) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib64/tls/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib64/tls", 0xffffe28d40)        = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib64/octeon2/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib64/octeon2", 0xffffe28d40)    = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib64/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\10\0\0\0\1\0\0\0\0\0\0\22P"..., 832) = 832
lseek(3, 2232, SEEK_SET)                = 2232
read(3, "\0\0\0\4\0\0\0\20\0\0\0\1GNU\0\0\0\0\0\0\0\0\2\0\0\0\6\0\0\0 ", 32) = 32
fstat(3, {st_mode=S_IFREG|0755, st_size=15856, ...}) = 0
mmap(NULL, 78272, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xfff414c000
mprotect(0xfff414f000, 61440, PROT_NONE) = 0
mmap(0xfff415e000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0xfff415e000
close(3)                                = 0
openat(AT_FDCWD, "tls/octeon2/libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "octeon2/libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib64/libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib64/tls/octeon2/libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib64/tls/octeon2", 0xffffe28d10) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib64/tls/libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib64/tls", 0xffffe28d10)    = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib64/octeon2/libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib64/octeon2", 0xffffe28d10) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib64/libdevmapper.so.1.02", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\10\0\0\0\1\0\0\0\0\0\0\254\240"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0555, st_size=527792, ...}) = 0
mmap(NULL, 566368, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xfff40c1000
mprotect(0xfff4136000, 65536, PROT_NONE) = 0
mmap(0xfff4146000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x75000) = 0xfff4146000
mmap(0xfff414b000, 1120, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xfff414b000
close(3)                                = 0
openat(AT_FDCWD, "tls/octeon2/libaio.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/libaio.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "octeon2/libaio.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "libaio.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/libaio.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib64/libaio.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\10\0\0\0\1\0\0\0\0\0\0\7\300"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=5200, ...}) = 0
mmap(NULL, 68928, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xfff40b0000
mprotect(0xfff40b1000, 61440, PROT_NONE) = 0
mmap(0xfff40c0000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0xfff40c0000
close(3)                                = 0
openat(AT_FDCWD, "tls/octeon2/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "octeon2/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\10\0\0\0\1\0\0\0\0\0\4\7H"..., 832) = 832
lseek(3, 88976, SEEK_SET)               = 88976
read(3, "\0\0\0\4\0\0\0\20\0\0\0\1GNU\0\0\0\0\0\0\0\0\2\0\0\0\6\0\0\0 ", 32) = 32
fstat(3, {st_mode=S_IFREG|0755, st_size=1856416, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xfff418d000
mmap(NULL, 1835664, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xfff3eef000
mprotect(0xfff4091000, 65536, PROT_NONE) = 0
mmap(0xfff40a1000, 45056, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a2000) = 0xfff40a1000
mmap(0xfff40ac000, 12944, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xfff40ac000
close(3)                                = 0
openat(AT_FDCWD, "tls/octeon2/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "octeon2/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib64/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\10\0\0\0\1\0\0\0\0\0\0\213\0"..., 832) = 832
lseek(3, 14976, SEEK_SET)               = 14976
read(3, "\0\0\0\4\0\0\0\20\0\0\0\1GNU\0\0\0\0\0\0\0\0\2\0\0\0\6\0\0\0 ", 32) = 32
fstat(3, {st_mode=S_IFREG|0755, st_size=145008, ...}) = 0
mmap(NULL, 215000, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xfff3eba000
mprotect(0xfff3eda000, 61440, PROT_NONE) = 0
mmap(0xfff3ee9000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1f000) = 0xfff3ee9000
mmap(0xfff3eeb000, 14296, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xfff3eeb000
close(3)                                = 0
openat(AT_FDCWD, "tls/octeon2/libm.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/libm.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "octeon2/libm.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "libm.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/libm.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib64/libm.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\10\0\0\0\1\0\0\0\0\0\1G\320"..., 832) = 832
lseek(3, 38864, SEEK_SET)               = 38864
read(3, "\0\0\0\4\0\0\0\20\0\0\0\1GNU\0\0\0\0\0\0\0\0\2\0\0\0\6\0\0\0 ", 32) = 32
fstat(3, {st_mode=S_IFREG|0755, st_size=1129144, ...}) = 0
mmap(NULL, 1170288, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xfff3d9c000
mprotect(0xfff3ea9000, 61440, PROT_NONE) = 0
mmap(0xfff3eb8000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x10c000) = 0xfff3eb8000
close(3)                                = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xfff418b000
set_thread_area(0xfff4193290)           = 0
mprotect(0xfff40a1000, 24576, PROT_READ) = 0
mprotect(0xfff3eb8000, 4096, PROT_READ) = 0
mprotect(0xfff3ee9000, 4096, PROT_READ) = 0
mprotect(0xfff4146000, 4096, PROT_READ) = 0
mprotect(0xfff415e000, 4096, PROT_READ) = 0
mprotect(0xaab6680000, 32768, PROT_READ) = 0
mprotect(0xfff4194000, 4096, PROT_READ) = 0
munmap(0xfff418f000, 64)                = 0
set_tid_address(0xfff418bc60)           = 1273
set_robust_list(0xfff418bc70, 24)       = 0
rt_sigaction(SIGRTMIN, {sa_handler=0xfff3ec2428, sa_mask=[], sa_flags=SA_SIGINFO}, NULL, 16) = 0
rt_sigaction(SIGRT_1, {sa_handler=0xfff3ec2558, sa_mask=[], sa_flags=SA_RESTART|SA_SIGINFO}, NULL, 16) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 16) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0
fcntl(2, F_GETFD)                       = 0
fcntl(0, F_GETFD)                       = 0
fcntl(1, F_GETFD)                       = 0
fcntl(2, F_GETFD)                       = 0
getppid()                               = 1271
openat(AT_FDCWD, "/proc/1271/cmdline", O_RDONLY) = 3
read(3, "strace\0pvcreate\0-ffy\0/dev/sda3\0", 31) = 31
close(3)                                = 0
openat(AT_FDCWD, "/proc/self/fd", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0500, st_size=0, ...}) = 0
brk(NULL)                               = 0xaabbe4d000
brk(0xaabbe6e000)                       = 0xaabbe6e000
getdents(3, /* 6 entries */, 32768)     = 144
getdents(3, /* 0 entries */, 32768)     = 0
close(3)                                = 0
gettid()                                = 1273
getpid()                                = 1273
fcntl(0, F_GETFD)                       = 0
fcntl(0, F_GETFL)                       = 0x2002 (flags O_RDWR|O_LARGEFILE)
dup(0)                                  = 3
close(0)                                = 0
dup2(3, 0)                              = 0
close(3)                                = 0
fcntl(0, F_GETFL)                       = 0x2002 (flags O_RDWR|O_LARGEFILE)
fcntl(1, F_GETFD)                       = 0
fcntl(1, F_GETFL)                       = 0x2002 (flags O_RDWR|O_LARGEFILE)
dup(1)                                  = 3
close(1)                                = 0
dup2(3, 1)                              = 1
close(3)                                = 0
fcntl(1, F_GETFL)                       = 0x2002 (flags O_RDWR|O_LARGEFILE)
stat("/etc/lvm", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
stat("/etc/lvm/lvm.conf", {st_mode=S_IFREG|0644, st_size=93568, ...}) = 0
stat("/etc/lvm/lvm.conf", {st_mode=S_IFREG|0644, st_size=93568, ...}) = 0
openat(AT_FDCWD, "/etc/lvm/lvm.conf", O_RDONLY) = 3
mmap(NULL, 93568, PROT_READ, MAP_PRIVATE, 3, 0) = 0xfff3d85000
munmap(0xfff3d85000, 93568)             = 0
close(3)                                = 0
gettimeofday({tv_sec=1599745840, tv_usec=916751}, NULL) = 0
openat(AT_FDCWD, "/etc/localtime", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
uname({sysname="Linux", nodename="(none)", ...}) = 0
stat("/etc/lvm/lvmlocal.conf", {st_mode=S_IFREG|0644, st_size=2301, ...}) = 0
stat("/etc/lvm/lvmlocal.conf", {st_mode=S_IFREG|0644, st_size=2301, ...}) = 0
openat(AT_FDCWD, "/etc/lvm/lvmlocal.conf", O_RDONLY) = 3
mmap(NULL, 2301, PROT_READ, MAP_PRIVATE, 3, 0) = 0xfff418f000
munmap(0xfff418f000, 2301)              = 0
close(3)                                = 0
umask(077)                              = 022
stat("/proc", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
openat(AT_FDCWD, "/proc/mounts", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3, "rootfs / rootfs rw 0 0\nproc /pro"..., 1024) = 1024
close(3)                                = 0
brk(0xaabbe90000)                       = 0xaabbe90000
openat(AT_FDCWD, "/proc/devices", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3, "Character devices:\n  1 mem\n  4 t"..., 1024) = 399
read(3, "", 1024)                       = 0
close(3)                                = 0
stat("/dev", {st_mode=S_IFDIR|0755, st_size=1440, ...}) = 0
openat(AT_FDCWD, "/dev/urandom", O_RDONLY) = 3
read(3, "\275\343\235\220", 4)          = 4
close(3)                                = 0
sysinfo({uptime=27753, loads=[0, 0, 0], totalram=16423124992, freeram=15895031808, sharedram=42950656, bufferram=8273920, totalswap=0, freeswap=0, procs=97, totalhigh=0, freehigh=0, mem_unit=1}) = 0
getuid()                                = 0
geteuid()                               = 0
stat("/etc/lvm/lvm.conf", {st_mode=S_IFREG|0644, st_size=93568, ...}) = 0
stat("/etc/lvm/lvmlocal.conf", {st_mode=S_IFREG|0644, st_size=2301, ...}) = 0
access("/run/lvmetad.pid", F_OK)        = -1 ENOENT (No such file or directory)
stat("/sys/subsystem/block/devices", 0xffffe289f0) = -1 ENOENT (No such file or directory)
stat("/sys/class/block", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
stat("/etc/lvm/cache/.cache", {st_mode=S_IFREG|0600, st_size=77, ...}) = 0
stat("/etc/lvm/cache/.cache", {st_mode=S_IFREG|0600, st_size=77, ...}) = 0
stat("/etc/lvm/cache/.cache", {st_mode=S_IFREG|0600, st_size=77, ...}) = 0
stat("/etc/lvm/cache/.cache", {st_mode=S_IFREG|0600, st_size=77, ...}) = 0
openat(AT_FDCWD, "/etc/lvm/cache/.cache", O_RDONLY) = 3
mmap(NULL, 77, PROT_READ, MAP_PRIVATE, 3, 0) = 0xfff418f000
munmap(0xfff418f000, 77)                = 0
close(3)                                = 0
getpid()                                = 1273
rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], [], 16) = 0
write(2, "  ", 2  )                       = 2
write(2, "Read-only locking type set. Writ"..., 55Read-only locking type set. Write locks are prohibited.) = 55
write(2, "\n", 1
)                       = 1
rt_sigprocmask(SIG_SETMASK, [], NULL, 16) = 0
write(2, "  ", 2  )                       = 2
write(2, "Can't get lock for orphan PVs.", 30Can't get lock for orphan PVs.) = 30
write(2, "\n", 1
)                       = 1
fcntl(0, F_GETFD)                       = 0
fcntl(0, F_GETFL)                       = 0x2002 (flags O_RDWR|O_LARGEFILE)
dup(0)                                  = 3
close(0)                                = 0
dup2(3, 0)                              = 0
close(3)                                = 0
fcntl(0, F_GETFL)                       = 0x2002 (flags O_RDWR|O_LARGEFILE)
fcntl(1, F_GETFD)                       = 0
fcntl(1, F_GETFL)                       = 0x2002 (flags O_RDWR|O_LARGEFILE)
dup(1)                                  = 3
close(1)                                = 0
dup2(3, 1)                              = 1
close(3)                                = 0
fcntl(1, F_GETFL)                       = 0x2002 (flags O_RDWR|O_LARGEFILE)
exit_group(5)                           = ?
+++ exited with 5 +++
bash-4.4#
bash-4.4#
bash-4.4#
bash-4.4#
bash-4.4# pvcreate -vvvv /dev/sda3
#lvmcmdline.c:2814          Parsing: pvcreate -vvvv /dev/sda3
#lvmcmdline.c:1868          Recognised command pvcreate_general (id 100 / enum 79).
#config/config.c:1480        devices/global_filter not found in config: defaulting to global_filter = [ "a|.*/|" ]
#filters/filter-sysfs.c:327           Sysfs filter initialised.
#filters/filter-internal.c:77            Internal filter initialised.
#filters/filter-regex.c:216           Regex filter initialised.
#filters/filter-type.c:56            LVM type filter initialised.
#filters/filter-usable.c:183           Usable device filter initialised.
#filters/filter-mpath.c:291           mpath filter initialised.
#filters/filter-partitioned.c:69            Partitioned filter initialised.
#filters/filter-signature.c:84            signature filter initialised.
#filters/filter-md.c:169           MD filter initialised.
#filters/filter-composite.c:109           Composite filter initialised.
#libdm-config.c:975         devices/cache not found in config: defaulting to /etc/lvm/cache/.cache
#filters/filter-persistent.c:415           Persistent filter initialised.
#device/dev-io.c:609           Opened /etc/lvm/cache/.cache RO
#filters/filter-persistent.c:145           Loading persistent filter cache from /etc/lvm/cache/.cache
#filters/filter-persistent.c:89          Couldn't find persistent_filter_cache/valid_devices array in '/etc/lvm/cache/.cache'
#filters/filter-persistent.c:152         Loaded persistent filter cache from /etc/lvm/cache/.cache
#device/dev-io.c:658           Closed /etc/lvm/cache/.cache
#commands/toolcontext.c:1289      Failed to load existing device cache from /etc/lvm/cache/.cache
#libdm-config.c:1074        metadata/record_lvs_history not found in config: defaulting to 0
#lvmcmdline.c:2882          DEGRADED MODE. Incomplete RAID LVs will be processed.
#lvmcmdline.c:2888          Processing command: pvcreate -vvvv /dev/sda3
#lvmcmdline.c:2889          Command pid: 1274
#lvmcmdline.c:2890          System ID:
#lvmcmdline.c:2893          O_DIRECT will be used
#locking/locking.c:181       Read-only locking selected. Only read operations permitted.
#libdm-config.c:1074        metadata/pvmetadataignore not found in config: defaulting to 0
#libdm-config.c:1002        metadata/pvmetadatasize not found in config: defaulting to 255
#libdm-config.c:1002        metadata/pvmetadatacopies not found in config: defaulting to 1
#libdm-config.c:975         report/output_format not found in config: defaulting to basic
#libdm-config.c:1074        log/report_command_log not found in config: defaulting to 0
#cache/lvmcache.c:2535          Dropping VG info
#cache/lvmcache.c:751           lvmcache has no info for vgname "#orphans_lvm2" with VGID #orphans_lvm2.
#cache/lvmcache.c:751           lvmcache has no info for vgname "#orphans_lvm2".
#cache/lvmcache.c:2082          lvmcache: Initialised VG #orphans_lvm2.
#locking/locking.c:331           Dropping cache for #orphans.
#locking/no_locking.c:89      Read-only locking type set. Write locks are prohibited.
#locking/locking.c:275           <backtrace>
#locking/locking.c:352           <backtrace>
#toollib.c:5482    Can't get lock for orphan PVs.
#cache/lvmcache.c:2535          Dropping VG info
#cache/lvmcache.c:751           lvmcache has no info for vgname "#orphans_lvm2" with VGID #orphans_lvm2.
#cache/lvmcache.c:751           lvmcache has no info for vgname "#orphans_lvm2".
#cache/lvmcache.c:2082          lvmcache: Initialised VG #orphans_lvm2.
#lvmcmdline.c:3028          Completed: pvcreate -vvvv /dev/sda3
bash-4.4#

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180
  2020-09-10 13:53 [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180 KrishnaMurali Chennuboina
@ 2020-09-14 14:58 ` Roger Heflin
  2020-09-14 15:19   ` KrishnaMurali Chennuboina
  0 siblings, 1 reply; 8+ messages in thread
From: Roger Heflin @ 2020-09-14 14:58 UTC (permalink / raw)
  To: LVM general discussion and development

In general I would suggest fully disabling lvmetad from the config
files and from being started up.

Issues around it not answering (like above) and answering but somehow
having stale/wrong info have burned me too many times to trust it.  It
may be a lvmetad bug, or be udevd weirdness.

The only significant improvement it makes is it reduces the lvm
command time on installs with significant numbers of devices, but
given that the info has been wrong often enough that is not worth the
risk.

On Mon, Sep 14, 2020 at 2:25 AM KrishnaMurali Chennuboina
<krishchennu414@gmail.com> wrote:
>
> Hi Team,
>
> While trying to analyze one the issue, we felt that upgrading the current LVM2 package in our repository will be the best approach.
> As part of that, we have updated the respective package from  2.02.176 to 2.02.180. We have verified the same and booted x86_64 hardware without any issues.
>
> But while trying to boot mips64 hardware we have started observing the below issue.  Providing the snippet of the log,
>
> # executing command: vgchange -an
> (status, output): (0,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.)
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>
> Attached the detailed log for reference. There is no other change included other than the LVM2 update.
>
> LVM2 Version: 2.02.176
> Updated LVM2 version: 2.02.180
>
> Please share inputs on why this issue is being observed with .180 version?
> Please let me know if i can share any other information.
>
> 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/

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180
  2020-09-14 14:58 ` Roger Heflin
@ 2020-09-14 15:19   ` KrishnaMurali Chennuboina
  2020-09-15 11:05     ` Roger Heflin
  0 siblings, 1 reply; 8+ messages in thread
From: KrishnaMurali Chennuboina @ 2020-09-14 15:19 UTC (permalink / raw)
  To: LVM general discussion and development

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

Hi Roger,

I have tried this with the older LVM package(.176) and this issue was not
seen. Issue was seen with .180 version every time.
# executing command: vgchange -ay
(status, output): (0,   WARNING: Failed to connect to lvmetad. Falling back
to device scanning.)
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
# executing command: pvcreate -ffy /dev/sda3
(status, output): (5,   WARNING: Failed to connect to lvmetad. Falling back
to device scanning.
  Error reading device /dev/sda3 at 0 length 4096.
  Error reading device /dev/ram0 at 0 length 4096.
  Error reading device /dev/loop0 at 0 length 4096.
  Error reading device /dev/sda at 0 length 512.
  Error reading device /dev/sda at 0 length 4096.
  Error reading device /dev/ram1 at 0 length 4096.
  Error reading device /dev/sda1 at 0 length 4096.
  Error reading device /dev/ram2 at 0 length 4096.
  Error reading device /dev/sda2 at 0 length 4096.
  Error reading device /dev/ram3 at 0 length 4096.
  Error reading device /dev/ram4 at 0 length 4096.
  Error reading device /dev/ram5 at 0 length 4096.
  Error reading device /dev/ram6 at 0 length 4096.
  Error reading device /dev/ram7 at 0 length 4096.
  Error reading device /dev/ram8 at 0 length 4096.
  Error reading device /dev/ram9 at 0 length 4096.
  Error reading device /dev/ram10 at 0 length 4096.
  Error reading device /dev/ram11 at 0 length 4096.
  Error reading device /dev/ram12 at 0 length 4096.
  Error reading device /dev/ram13 at 0 length 4096.
  Error reading device /dev/ram14 at 0 length 4096.
  Error reading device /dev/ram15 at 0 length 4096.
  Device /dev/sda3 excluded by a filter.)
Failed to execute command: pvcreate -ffy /dev/sda3
ec=0

I have tried with different options of pvcreate but didnt helped much.
After the system got halted with the above error, i tried to executing pvs
command but got the below error.
bash-4.4# pvs
  Error reading device /dev/ram0 at 0 length 4096.
  Error reading device /dev/loop0 at 0 length 4096.
  Error reading device /dev/sda at 0 length 512.
  Error reading device /dev/sda at 0 length 4096.
  Error reading device /dev/ram1 at 0 length 4096.
  Error reading device /dev/sda1 at 0 length 4096.
  Error reading device /dev/ram2 at 0 length 4096.
  Error reading device /dev/sda2 at 0 length 4096.
  Error reading device /dev/ram3 at 0 length 4096.
  Error reading device /dev/sda3 at 0 length 4096.
  Error reading device /dev/ram4 at 0 length 4096.
  Error reading device /dev/sda4 at 0 length 4096.
  Error reading device /dev/ram5 at 0 length 4096.
  Error reading device /dev/ram6 at 0 length 4096.
  Error reading device /dev/ram7 at 0 length 4096.
  Error reading device /dev/ram8 at 0 length 4096.
  Error reading device /dev/ram9 at 0 length 4096.
  Error reading device /dev/ram10 at 0 length 4096.
  Error reading device /dev/ram11 at 0 length 4096.
  Error reading device /dev/ram12 at 0 length 4096.
  Error reading device /dev/ram13 at 0 length 4096.
  Error reading device /dev/ram14 at 0 length 4096.
  Error reading device /dev/ram15 at 0 length 4096.
  Error reading device /dev/sdb at 0 length 512.
  Error reading device /dev/sdb at 0 length 4096.
  Error reading device /dev/sdb1 at 0 length 4096.
  Error reading device /dev/sdb2 at 0 length 4096.
  Error reading device /dev/sdb3 at 0 length 4096.
  Read-only locking type set. Write locks are prohibited.
  Recovery of standalone physical volumes failed.
  Cannot process standalone physical volumes
bash-4.4#

Attached the complete log in initial mail.

Thanks.

On Mon, 14 Sep 2020 at 20:29, Roger Heflin <rogerheflin@gmail.com> wrote:

> In general I would suggest fully disabling lvmetad from the config
> files and from being started up.
>
> Issues around it not answering (like above) and answering but somehow
> having stale/wrong info have burned me too many times to trust it.  It
> may be a lvmetad bug, or be udevd weirdness.
>
> The only significant improvement it makes is it reduces the lvm
> command time on installs with significant numbers of devices, but
> given that the info has been wrong often enough that is not worth the
> risk.
>
> On Mon, Sep 14, 2020 at 2:25 AM KrishnaMurali Chennuboina
> <krishchennu414@gmail.com> wrote:
> >
> > Hi Team,
> >
> > While trying to analyze one the issue, we felt that upgrading the
> current LVM2 package in our repository will be the best approach.
> > As part of that, we have updated the respective package from  2.02.176
> to 2.02.180. We have verified the same and booted x86_64 hardware without
> any issues.
> >
> > But while trying to boot mips64 hardware we have started observing the
> below issue.  Providing the snippet of the log,
> >
> > # executing command: vgchange -an
> > (status, output): (0,   WARNING: Failed to connect to lvmetad. Falling
> back to device scanning.)
> >   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
> >
> > Attached the detailed log for reference. There is no other change
> included other than the LVM2 update.
> >
> > LVM2 Version: 2.02.176
> > Updated LVM2 version: 2.02.180
> >
> > Please share inputs on why this issue is being observed with .180
> version?
> > Please let me know if i can share any other information.
> >
> > 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/
>
> _______________________________________________
> 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/
>
>

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

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180
  2020-09-14 15:19   ` KrishnaMurali Chennuboina
@ 2020-09-15 11:05     ` Roger Heflin
  2020-09-15 12:58       ` KrishnaMurali Chennuboina
  2020-09-15 18:46       ` Zdenek Kabelac
  0 siblings, 2 replies; 8+ messages in thread
From: Roger Heflin @ 2020-09-15 11:05 UTC (permalink / raw)
  To: LVM general discussion and development

#1:
Device /dev/sda3 excluded by a filter.)
Failed to execute command: pvcreate -ffy /dev/sda3
ec=0

excluded by filter is likely the issue, I think there was a bug were
it allowed that pvcreate to work when it should have blocked it
because of the filter.  It should not allow a pvcreate against
something blocked by a filter.

#2: Read-only locking type set. Write locks are prohibited.
I am going to guess either / is not mounted rw, or you don't have the
directory mounted rw that is needed to create the locks (/var/run/lvm
usually).

On Tue, Sep 15, 2020 at 1:42 AM KrishnaMurali Chennuboina
<krishchennu414@gmail.com> wrote:
>
> Hi Roger,
>
> I have tried this with the older LVM package(.176) and this issue was not seen. Issue was seen with .180 version every time.
> # executing command: vgchange -ay
> (status, output): (0,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.)
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
> # executing command: pvcreate -ffy /dev/sda3
> (status, output): (5,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   Error reading device /dev/sda3 at 0 length 4096.
>   Error reading device /dev/ram0 at 0 length 4096.
>   Error reading device /dev/loop0 at 0 length 4096.
>   Error reading device /dev/sda at 0 length 512.
>   Error reading device /dev/sda at 0 length 4096.
>   Error reading device /dev/ram1 at 0 length 4096.
>   Error reading device /dev/sda1 at 0 length 4096.
>   Error reading device /dev/ram2 at 0 length 4096.
>   Error reading device /dev/sda2 at 0 length 4096.
>   Error reading device /dev/ram3 at 0 length 4096.
>   Error reading device /dev/ram4 at 0 length 4096.
>   Error reading device /dev/ram5 at 0 length 4096.
>   Error reading device /dev/ram6 at 0 length 4096.
>   Error reading device /dev/ram7 at 0 length 4096.
>   Error reading device /dev/ram8 at 0 length 4096.
>   Error reading device /dev/ram9 at 0 length 4096.
>   Error reading device /dev/ram10 at 0 length 4096.
>   Error reading device /dev/ram11 at 0 length 4096.
>   Error reading device /dev/ram12 at 0 length 4096.
>   Error reading device /dev/ram13 at 0 length 4096.
>   Error reading device /dev/ram14 at 0 length 4096.
>   Error reading device /dev/ram15 at 0 length 4096.
>   Device /dev/sda3 excluded by a filter.)
> Failed to execute command: pvcreate -ffy /dev/sda3
> ec=0
>
> I have tried with different options of pvcreate but didnt helped much. After the system got halted with the above error, i tried to executing pvs command but got the below error.
> bash-4.4# pvs
>   Error reading device /dev/ram0 at 0 length 4096.
>   Error reading device /dev/loop0 at 0 length 4096.
>   Error reading device /dev/sda at 0 length 512.
>   Error reading device /dev/sda at 0 length 4096.
>   Error reading device /dev/ram1 at 0 length 4096.
>   Error reading device /dev/sda1 at 0 length 4096.
>   Error reading device /dev/ram2 at 0 length 4096.
>   Error reading device /dev/sda2 at 0 length 4096.
>   Error reading device /dev/ram3 at 0 length 4096.
>   Error reading device /dev/sda3 at 0 length 4096.
>   Error reading device /dev/ram4 at 0 length 4096.
>   Error reading device /dev/sda4 at 0 length 4096.
>   Error reading device /dev/ram5 at 0 length 4096.
>   Error reading device /dev/ram6 at 0 length 4096.
>   Error reading device /dev/ram7 at 0 length 4096.
>   Error reading device /dev/ram8 at 0 length 4096.
>   Error reading device /dev/ram9 at 0 length 4096.
>   Error reading device /dev/ram10 at 0 length 4096.
>   Error reading device /dev/ram11 at 0 length 4096.
>   Error reading device /dev/ram12 at 0 length 4096.
>   Error reading device /dev/ram13 at 0 length 4096.
>   Error reading device /dev/ram14 at 0 length 4096.
>   Error reading device /dev/ram15 at 0 length 4096.
>   Error reading device /dev/sdb at 0 length 512.
>   Error reading device /dev/sdb at 0 length 4096.
>   Error reading device /dev/sdb1 at 0 length 4096.
>   Error reading device /dev/sdb2 at 0 length 4096.
>   Error reading device /dev/sdb3 at 0 length 4096.
>   Read-only locking type set. Write locks are prohibited.
>   Recovery of standalone physical volumes failed.
>   Cannot process standalone physical volumes
> bash-4.4#
>
> Attached the complete log in initial mail.
>
> Thanks.
>
> On Mon, 14 Sep 2020 at 20:29, Roger Heflin <rogerheflin@gmail.com> wrote:
>>
>> In general I would suggest fully disabling lvmetad from the config
>> files and from being started up.
>>
>> Issues around it not answering (like above) and answering but somehow
>> having stale/wrong info have burned me too many times to trust it.  It
>> may be a lvmetad bug, or be udevd weirdness.
>>
>> The only significant improvement it makes is it reduces the lvm
>> command time on installs with significant numbers of devices, but
>> given that the info has been wrong often enough that is not worth the
>> risk.
>>
>> On Mon, Sep 14, 2020 at 2:25 AM KrishnaMurali Chennuboina
>> <krishchennu414@gmail.com> wrote:
>> >
>> > Hi Team,
>> >
>> > While trying to analyze one the issue, we felt that upgrading the current LVM2 package in our repository will be the best approach.
>> > As part of that, we have updated the respective package from  2.02.176 to 2.02.180. We have verified the same and booted x86_64 hardware without any issues.
>> >
>> > But while trying to boot mips64 hardware we have started observing the below issue.  Providing the snippet of the log,
>> >
>> > # executing command: vgchange -an
>> > (status, output): (0,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.)
>> >   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>> >
>> > Attached the detailed log for reference. There is no other change included other than the LVM2 update.
>> >
>> > LVM2 Version: 2.02.176
>> > Updated LVM2 version: 2.02.180
>> >
>> > Please share inputs on why this issue is being observed with .180 version?
>> > Please let me know if i can share any other information.
>> >
>> > 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/
>>
>> _______________________________________________
>> 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 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/

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180
  2020-09-15 11:05     ` Roger Heflin
@ 2020-09-15 12:58       ` KrishnaMurali Chennuboina
  2020-09-15 17:01         ` KrishnaMurali Chennuboina
  2020-09-15 18:46       ` Zdenek Kabelac
  1 sibling, 1 reply; 8+ messages in thread
From: KrishnaMurali Chennuboina @ 2020-09-15 12:58 UTC (permalink / raw)
  To: LVM general discussion and development

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

Hi Roger,

Thanks for the information shared.
Filter which we used in our conf file was,
        # Accept every block device:
          filter = [ "r|^/dev/drbd.*|" ]


Thanks.

On Tue, 15 Sep 2020 at 16:36, Roger Heflin <rogerheflin@gmail.com> wrote:

> #1:
> Device /dev/sda3 excluded by a filter.)
> Failed to execute command: pvcreate -ffy /dev/sda3
> ec=0
>
> excluded by filter is likely the issue, I think there was a bug were
> it allowed that pvcreate to work when it should have blocked it
> because of the filter.  It should not allow a pvcreate against
> something blocked by a filter.
>
> #2: Read-only locking type set. Write locks are prohibited.
> I am going to guess either / is not mounted rw, or you don't have the
> directory mounted rw that is needed to create the locks (/var/run/lvm
> usually).
>
> On Tue, Sep 15, 2020 at 1:42 AM KrishnaMurali Chennuboina
> <krishchennu414@gmail.com> wrote:
> >
> > Hi Roger,
> >
> > I have tried this with the older LVM package(.176) and this issue was
> not seen. Issue was seen with .180 version every time.
> > # executing command: vgchange -ay
> > (status, output): (0,   WARNING: Failed to connect to lvmetad. Falling
> back to device scanning.)
> >   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
> > # executing command: pvcreate -ffy /dev/sda3
> > (status, output): (5,   WARNING: Failed to connect to lvmetad. Falling
> back to device scanning.
> >   Error reading device /dev/sda3 at 0 length 4096.
> >   Error reading device /dev/ram0 at 0 length 4096.
> >   Error reading device /dev/loop0 at 0 length 4096.
> >   Error reading device /dev/sda at 0 length 512.
> >   Error reading device /dev/sda at 0 length 4096.
> >   Error reading device /dev/ram1 at 0 length 4096.
> >   Error reading device /dev/sda1 at 0 length 4096.
> >   Error reading device /dev/ram2 at 0 length 4096.
> >   Error reading device /dev/sda2 at 0 length 4096.
> >   Error reading device /dev/ram3 at 0 length 4096.
> >   Error reading device /dev/ram4 at 0 length 4096.
> >   Error reading device /dev/ram5 at 0 length 4096.
> >   Error reading device /dev/ram6 at 0 length 4096.
> >   Error reading device /dev/ram7 at 0 length 4096.
> >   Error reading device /dev/ram8 at 0 length 4096.
> >   Error reading device /dev/ram9 at 0 length 4096.
> >   Error reading device /dev/ram10 at 0 length 4096.
> >   Error reading device /dev/ram11 at 0 length 4096.
> >   Error reading device /dev/ram12 at 0 length 4096.
> >   Error reading device /dev/ram13 at 0 length 4096.
> >   Error reading device /dev/ram14 at 0 length 4096.
> >   Error reading device /dev/ram15 at 0 length 4096.
> >   Device /dev/sda3 excluded by a filter.)
> > Failed to execute command: pvcreate -ffy /dev/sda3
> > ec=0
> >
> > I have tried with different options of pvcreate but didnt helped much.
> After the system got halted with the above error, i tried to executing pvs
> command but got the below error.
> > bash-4.4# pvs
> >   Error reading device /dev/ram0 at 0 length 4096.
> >   Error reading device /dev/loop0 at 0 length 4096.
> >   Error reading device /dev/sda at 0 length 512.
> >   Error reading device /dev/sda at 0 length 4096.
> >   Error reading device /dev/ram1 at 0 length 4096.
> >   Error reading device /dev/sda1 at 0 length 4096.
> >   Error reading device /dev/ram2 at 0 length 4096.
> >   Error reading device /dev/sda2 at 0 length 4096.
> >   Error reading device /dev/ram3 at 0 length 4096.
> >   Error reading device /dev/sda3 at 0 length 4096.
> >   Error reading device /dev/ram4 at 0 length 4096.
> >   Error reading device /dev/sda4 at 0 length 4096.
> >   Error reading device /dev/ram5 at 0 length 4096.
> >   Error reading device /dev/ram6 at 0 length 4096.
> >   Error reading device /dev/ram7 at 0 length 4096.
> >   Error reading device /dev/ram8 at 0 length 4096.
> >   Error reading device /dev/ram9 at 0 length 4096.
> >   Error reading device /dev/ram10 at 0 length 4096.
> >   Error reading device /dev/ram11 at 0 length 4096.
> >   Error reading device /dev/ram12 at 0 length 4096.
> >   Error reading device /dev/ram13 at 0 length 4096.
> >   Error reading device /dev/ram14 at 0 length 4096.
> >   Error reading device /dev/ram15 at 0 length 4096.
> >   Error reading device /dev/sdb at 0 length 512.
> >   Error reading device /dev/sdb at 0 length 4096.
> >   Error reading device /dev/sdb1 at 0 length 4096.
> >   Error reading device /dev/sdb2 at 0 length 4096.
> >   Error reading device /dev/sdb3 at 0 length 4096.
> >   Read-only locking type set. Write locks are prohibited.
> >   Recovery of standalone physical volumes failed.
> >   Cannot process standalone physical volumes
> > bash-4.4#
> >
> > Attached the complete log in initial mail.
> >
> > Thanks.
> >
> > On Mon, 14 Sep 2020 at 20:29, Roger Heflin <rogerheflin@gmail.com>
> wrote:
> >>
> >> In general I would suggest fully disabling lvmetad from the config
> >> files and from being started up.
> >>
> >> Issues around it not answering (like above) and answering but somehow
> >> having stale/wrong info have burned me too many times to trust it.  It
> >> may be a lvmetad bug, or be udevd weirdness.
> >>
> >> The only significant improvement it makes is it reduces the lvm
> >> command time on installs with significant numbers of devices, but
> >> given that the info has been wrong often enough that is not worth the
> >> risk.
> >>
> >> On Mon, Sep 14, 2020 at 2:25 AM KrishnaMurali Chennuboina
> >> <krishchennu414@gmail.com> wrote:
> >> >
> >> > Hi Team,
> >> >
> >> > While trying to analyze one the issue, we felt that upgrading the
> current LVM2 package in our repository will be the best approach.
> >> > As part of that, we have updated the respective package from
> 2.02.176 to 2.02.180. We have verified the same and booted x86_64 hardware
> without any issues.
> >> >
> >> > But while trying to boot mips64 hardware we have started observing
> the below issue.  Providing the snippet of the log,
> >> >
> >> > # executing command: vgchange -an
> >> > (status, output): (0,   WARNING: Failed to connect to lvmetad.
> Falling back to device scanning.)
> >> >   WARNING: Failed to connect to lvmetad. Falling back to device
> scanning.
> >> >
> >> > Attached the detailed log for reference. There is no other change
> included other than the LVM2 update.
> >> >
> >> > LVM2 Version: 2.02.176
> >> > Updated LVM2 version: 2.02.180
> >> >
> >> > Please share inputs on why this issue is being observed with .180
> version?
> >> > Please let me know if i can share any other information.
> >> >
> >> > 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/
> >>
> >> _______________________________________________
> >> 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 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 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/
>
>

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

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180
  2020-09-15 12:58       ` KrishnaMurali Chennuboina
@ 2020-09-15 17:01         ` KrishnaMurali Chennuboina
  2020-09-17 16:26           ` Roger Heflin
  0 siblings, 1 reply; 8+ messages in thread
From: KrishnaMurali Chennuboina @ 2020-09-15 17:01 UTC (permalink / raw)
  To: LVM general discussion and development

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

Hi Roger,

Missed to add my comment in the earlier mail.
From the filter it should not exclude /dev/sda*. But not sure why it is
being excluded while executing pvcreate command.

Thanks.

On Tue, 15 Sep 2020 at 18:28, KrishnaMurali Chennuboina <
krishchennu414@gmail.com> wrote:

> Hi Roger,
>
> Thanks for the information shared.
> Filter which we used in our conf file was,
>         # Accept every block device:
>           filter = [ "r|^/dev/drbd.*|" ]
>
>
> Thanks.
>
> On Tue, 15 Sep 2020 at 16:36, Roger Heflin <rogerheflin@gmail.com> wrote:
>
>> #1:
>> Device /dev/sda3 excluded by a filter.)
>> Failed to execute command: pvcreate -ffy /dev/sda3
>> ec=0
>>
>> excluded by filter is likely the issue, I think there was a bug were
>> it allowed that pvcreate to work when it should have blocked it
>> because of the filter.  It should not allow a pvcreate against
>> something blocked by a filter.
>>
>> #2: Read-only locking type set. Write locks are prohibited.
>> I am going to guess either / is not mounted rw, or you don't have the
>> directory mounted rw that is needed to create the locks (/var/run/lvm
>> usually).
>>
>> On Tue, Sep 15, 2020 at 1:42 AM KrishnaMurali Chennuboina
>> <krishchennu414@gmail.com> wrote:
>> >
>> > Hi Roger,
>> >
>> > I have tried this with the older LVM package(.176) and this issue was
>> not seen. Issue was seen with .180 version every time.
>> > # executing command: vgchange -ay
>> > (status, output): (0,   WARNING: Failed to connect to lvmetad. Falling
>> back to device scanning.)
>> >   WARNING: Failed to connect to lvmetad. Falling back to device
>> scanning.
>> > # executing command: pvcreate -ffy /dev/sda3
>> > (status, output): (5,   WARNING: Failed to connect to lvmetad. Falling
>> back to device scanning.
>> >   Error reading device /dev/sda3 at 0 length 4096.
>> >   Error reading device /dev/ram0 at 0 length 4096.
>> >   Error reading device /dev/loop0 at 0 length 4096.
>> >   Error reading device /dev/sda at 0 length 512.
>> >   Error reading device /dev/sda at 0 length 4096.
>> >   Error reading device /dev/ram1 at 0 length 4096.
>> >   Error reading device /dev/sda1 at 0 length 4096.
>> >   Error reading device /dev/ram2 at 0 length 4096.
>> >   Error reading device /dev/sda2 at 0 length 4096.
>> >   Error reading device /dev/ram3 at 0 length 4096.
>> >   Error reading device /dev/ram4 at 0 length 4096.
>> >   Error reading device /dev/ram5 at 0 length 4096.
>> >   Error reading device /dev/ram6 at 0 length 4096.
>> >   Error reading device /dev/ram7 at 0 length 4096.
>> >   Error reading device /dev/ram8 at 0 length 4096.
>> >   Error reading device /dev/ram9 at 0 length 4096.
>> >   Error reading device /dev/ram10 at 0 length 4096.
>> >   Error reading device /dev/ram11 at 0 length 4096.
>> >   Error reading device /dev/ram12 at 0 length 4096.
>> >   Error reading device /dev/ram13 at 0 length 4096.
>> >   Error reading device /dev/ram14 at 0 length 4096.
>> >   Error reading device /dev/ram15 at 0 length 4096.
>> >   Device /dev/sda3 excluded by a filter.)
>> > Failed to execute command: pvcreate -ffy /dev/sda3
>> > ec=0
>> >
>> > I have tried with different options of pvcreate but didnt helped much.
>> After the system got halted with the above error, i tried to executing pvs
>> command but got the below error.
>> > bash-4.4# pvs
>> >   Error reading device /dev/ram0 at 0 length 4096.
>> >   Error reading device /dev/loop0 at 0 length 4096.
>> >   Error reading device /dev/sda at 0 length 512.
>> >   Error reading device /dev/sda at 0 length 4096.
>> >   Error reading device /dev/ram1 at 0 length 4096.
>> >   Error reading device /dev/sda1 at 0 length 4096.
>> >   Error reading device /dev/ram2 at 0 length 4096.
>> >   Error reading device /dev/sda2 at 0 length 4096.
>> >   Error reading device /dev/ram3 at 0 length 4096.
>> >   Error reading device /dev/sda3 at 0 length 4096.
>> >   Error reading device /dev/ram4 at 0 length 4096.
>> >   Error reading device /dev/sda4 at 0 length 4096.
>> >   Error reading device /dev/ram5 at 0 length 4096.
>> >   Error reading device /dev/ram6 at 0 length 4096.
>> >   Error reading device /dev/ram7 at 0 length 4096.
>> >   Error reading device /dev/ram8 at 0 length 4096.
>> >   Error reading device /dev/ram9 at 0 length 4096.
>> >   Error reading device /dev/ram10 at 0 length 4096.
>> >   Error reading device /dev/ram11 at 0 length 4096.
>> >   Error reading device /dev/ram12 at 0 length 4096.
>> >   Error reading device /dev/ram13 at 0 length 4096.
>> >   Error reading device /dev/ram14 at 0 length 4096.
>> >   Error reading device /dev/ram15 at 0 length 4096.
>> >   Error reading device /dev/sdb at 0 length 512.
>> >   Error reading device /dev/sdb at 0 length 4096.
>> >   Error reading device /dev/sdb1 at 0 length 4096.
>> >   Error reading device /dev/sdb2 at 0 length 4096.
>> >   Error reading device /dev/sdb3 at 0 length 4096.
>> >   Read-only locking type set. Write locks are prohibited.
>> >   Recovery of standalone physical volumes failed.
>> >   Cannot process standalone physical volumes
>> > bash-4.4#
>> >
>> > Attached the complete log in initial mail.
>> >
>> > Thanks.
>> >
>> > On Mon, 14 Sep 2020 at 20:29, Roger Heflin <rogerheflin@gmail.com>
>> wrote:
>> >>
>> >> In general I would suggest fully disabling lvmetad from the config
>> >> files and from being started up.
>> >>
>> >> Issues around it not answering (like above) and answering but somehow
>> >> having stale/wrong info have burned me too many times to trust it.  It
>> >> may be a lvmetad bug, or be udevd weirdness.
>> >>
>> >> The only significant improvement it makes is it reduces the lvm
>> >> command time on installs with significant numbers of devices, but
>> >> given that the info has been wrong often enough that is not worth the
>> >> risk.
>> >>
>> >> On Mon, Sep 14, 2020 at 2:25 AM KrishnaMurali Chennuboina
>> >> <krishchennu414@gmail.com> wrote:
>> >> >
>> >> > Hi Team,
>> >> >
>> >> > While trying to analyze one the issue, we felt that upgrading the
>> current LVM2 package in our repository will be the best approach.
>> >> > As part of that, we have updated the respective package from
>> 2.02.176 to 2.02.180. We have verified the same and booted x86_64 hardware
>> without any issues.
>> >> >
>> >> > But while trying to boot mips64 hardware we have started observing
>> the below issue.  Providing the snippet of the log,
>> >> >
>> >> > # executing command: vgchange -an
>> >> > (status, output): (0,   WARNING: Failed to connect to lvmetad.
>> Falling back to device scanning.)
>> >> >   WARNING: Failed to connect to lvmetad. Falling back to device
>> scanning.
>> >> >
>> >> > Attached the detailed log for reference. There is no other change
>> included other than the LVM2 update.
>> >> >
>> >> > LVM2 Version: 2.02.176
>> >> > Updated LVM2 version: 2.02.180
>> >> >
>> >> > Please share inputs on why this issue is being observed with .180
>> version?
>> >> > Please let me know if i can share any other information.
>> >> >
>> >> > 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/
>> >>
>> >> _______________________________________________
>> >> 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 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 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/
>>
>>

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

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180
  2020-09-15 11:05     ` Roger Heflin
  2020-09-15 12:58       ` KrishnaMurali Chennuboina
@ 2020-09-15 18:46       ` Zdenek Kabelac
  1 sibling, 0 replies; 8+ messages in thread
From: Zdenek Kabelac @ 2020-09-15 18:46 UTC (permalink / raw)
  To: LVM general discussion and development, Roger Heflin

Dne 15. 09. 20 v 13:05 Roger Heflin napsal(a):
> #1:
> Device /dev/sda3 excluded by a filter.)
> Failed to execute command: pvcreate -ffy /dev/sda3
> ec=0
> 
> excluded by filter is likely the issue, I think there was a bug were
> it allowed that pvcreate to work when it should have blocked it
> because of the filter.  It should not allow a pvcreate against
> something blocked by a filter.
> 
> #2: Read-only locking type set. Write locks are prohibited.
> I am going to guess either / is not mounted rw, or you don't have the
> directory mounted rw that is needed to create the locks (/var/run/lvm
> usually).
> 
> On Tue, Sep 15, 2020 at 1:42 AM KrishnaMurali Chennuboina
> <krishchennu414@gmail.com> wrote:
>>

Hi

Please consider first to use the recent/upstream version of lvm2
(ATM either 2.02.187  or  2.03.10 or git  master/stable-2.0)

Unfortunately we can't be analyzing all the bugs from all the versions out there.

So please try to provide reproducer with versions listed above.
If you can't reproduced - then you may try to bisect to discover fixing patch.

If you need to fix a particular version on your distro,
you may need to ask your package maintainer to backport
list of patches for you.
In some case however this might be hard - aka it might be more efficient
to simply go with newer version.

Regards

Zdenek

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180
  2020-09-15 17:01         ` KrishnaMurali Chennuboina
@ 2020-09-17 16:26           ` Roger Heflin
  0 siblings, 0 replies; 8+ messages in thread
From: Roger Heflin @ 2020-09-17 16:26 UTC (permalink / raw)
  To: LVM general discussion and development

There is only a reject, there are no included devices.  Once you add a
filter it overrides the default filter including all I believe.

The fixes may have been fixing filtering as once you specify a filter
then there is no implied include (anymore). You should probably look
at the list of fixes that happened between those 2 versions.


On Thu, Sep 17, 2020 at 2:25 AM KrishnaMurali Chennuboina
<krishchennu414@gmail.com> wrote:
>
> Hi Roger,
>
> Missed to add my comment in the earlier mail.
> From the filter it should not exclude /dev/sda*. But not sure why it is being excluded while executing pvcreate command.
>
> Thanks.
>
> On Tue, 15 Sep 2020 at 18:28, KrishnaMurali Chennuboina <krishchennu414@gmail.com> wrote:
>>
>> Hi Roger,
>>
>> Thanks for the information shared.
>> Filter which we used in our conf file was,
>>         # Accept every block device:
>>           filter = [ "r|^/dev/drbd.*|" ]
>>
>>
>> Thanks.
>>
>> On Tue, 15 Sep 2020 at 16:36, Roger Heflin <rogerheflin@gmail.com> wrote:
>>>
>>> #1:
>>> Device /dev/sda3 excluded by a filter.)
>>> Failed to execute command: pvcreate -ffy /dev/sda3
>>> ec=0
>>>
>>> excluded by filter is likely the issue, I think there was a bug were
>>> it allowed that pvcreate to work when it should have blocked it
>>> because of the filter.  It should not allow a pvcreate against
>>> something blocked by a filter.
>>>
>>> #2: Read-only locking type set. Write locks are prohibited.
>>> I am going to guess either / is not mounted rw, or you don't have the
>>> directory mounted rw that is needed to create the locks (/var/run/lvm
>>> usually).
>>>
>>> On Tue, Sep 15, 2020 at 1:42 AM KrishnaMurali Chennuboina
>>> <krishchennu414@gmail.com> wrote:
>>> >
>>> > Hi Roger,
>>> >
>>> > I have tried this with the older LVM package(.176) and this issue was not seen. Issue was seen with .180 version every time.
>>> > # executing command: vgchange -ay
>>> > (status, output): (0,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.)
>>> >   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>> > # executing command: pvcreate -ffy /dev/sda3
>>> > (status, output): (5,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>> >   Error reading device /dev/sda3 at 0 length 4096.
>>> >   Error reading device /dev/ram0 at 0 length 4096.
>>> >   Error reading device /dev/loop0 at 0 length 4096.
>>> >   Error reading device /dev/sda at 0 length 512.
>>> >   Error reading device /dev/sda at 0 length 4096.
>>> >   Error reading device /dev/ram1 at 0 length 4096.
>>> >   Error reading device /dev/sda1 at 0 length 4096.
>>> >   Error reading device /dev/ram2 at 0 length 4096.
>>> >   Error reading device /dev/sda2 at 0 length 4096.
>>> >   Error reading device /dev/ram3 at 0 length 4096.
>>> >   Error reading device /dev/ram4 at 0 length 4096.
>>> >   Error reading device /dev/ram5 at 0 length 4096.
>>> >   Error reading device /dev/ram6 at 0 length 4096.
>>> >   Error reading device /dev/ram7 at 0 length 4096.
>>> >   Error reading device /dev/ram8 at 0 length 4096.
>>> >   Error reading device /dev/ram9 at 0 length 4096.
>>> >   Error reading device /dev/ram10 at 0 length 4096.
>>> >   Error reading device /dev/ram11 at 0 length 4096.
>>> >   Error reading device /dev/ram12 at 0 length 4096.
>>> >   Error reading device /dev/ram13 at 0 length 4096.
>>> >   Error reading device /dev/ram14 at 0 length 4096.
>>> >   Error reading device /dev/ram15 at 0 length 4096.
>>> >   Device /dev/sda3 excluded by a filter.)
>>> > Failed to execute command: pvcreate -ffy /dev/sda3
>>> > ec=0
>>> >
>>> > I have tried with different options of pvcreate but didnt helped much. After the system got halted with the above error, i tried to executing pvs command but got the below error.
>>> > bash-4.4# pvs
>>> >   Error reading device /dev/ram0 at 0 length 4096.
>>> >   Error reading device /dev/loop0 at 0 length 4096.
>>> >   Error reading device /dev/sda at 0 length 512.
>>> >   Error reading device /dev/sda at 0 length 4096.
>>> >   Error reading device /dev/ram1 at 0 length 4096.
>>> >   Error reading device /dev/sda1 at 0 length 4096.
>>> >   Error reading device /dev/ram2 at 0 length 4096.
>>> >   Error reading device /dev/sda2 at 0 length 4096.
>>> >   Error reading device /dev/ram3 at 0 length 4096.
>>> >   Error reading device /dev/sda3 at 0 length 4096.
>>> >   Error reading device /dev/ram4 at 0 length 4096.
>>> >   Error reading device /dev/sda4 at 0 length 4096.
>>> >   Error reading device /dev/ram5 at 0 length 4096.
>>> >   Error reading device /dev/ram6 at 0 length 4096.
>>> >   Error reading device /dev/ram7 at 0 length 4096.
>>> >   Error reading device /dev/ram8 at 0 length 4096.
>>> >   Error reading device /dev/ram9 at 0 length 4096.
>>> >   Error reading device /dev/ram10 at 0 length 4096.
>>> >   Error reading device /dev/ram11 at 0 length 4096.
>>> >   Error reading device /dev/ram12 at 0 length 4096.
>>> >   Error reading device /dev/ram13 at 0 length 4096.
>>> >   Error reading device /dev/ram14 at 0 length 4096.
>>> >   Error reading device /dev/ram15 at 0 length 4096.
>>> >   Error reading device /dev/sdb at 0 length 512.
>>> >   Error reading device /dev/sdb at 0 length 4096.
>>> >   Error reading device /dev/sdb1 at 0 length 4096.
>>> >   Error reading device /dev/sdb2 at 0 length 4096.
>>> >   Error reading device /dev/sdb3 at 0 length 4096.
>>> >   Read-only locking type set. Write locks are prohibited.
>>> >   Recovery of standalone physical volumes failed.
>>> >   Cannot process standalone physical volumes
>>> > bash-4.4#
>>> >
>>> > Attached the complete log in initial mail.
>>> >
>>> > Thanks.
>>> >
>>> > On Mon, 14 Sep 2020 at 20:29, Roger Heflin <rogerheflin@gmail.com> wrote:
>>> >>
>>> >> In general I would suggest fully disabling lvmetad from the config
>>> >> files and from being started up.
>>> >>
>>> >> Issues around it not answering (like above) and answering but somehow
>>> >> having stale/wrong info have burned me too many times to trust it.  It
>>> >> may be a lvmetad bug, or be udevd weirdness.
>>> >>
>>> >> The only significant improvement it makes is it reduces the lvm
>>> >> command time on installs with significant numbers of devices, but
>>> >> given that the info has been wrong often enough that is not worth the
>>> >> risk.
>>> >>
>>> >> On Mon, Sep 14, 2020 at 2:25 AM KrishnaMurali Chennuboina
>>> >> <krishchennu414@gmail.com> wrote:
>>> >> >
>>> >> > Hi Team,
>>> >> >
>>> >> > While trying to analyze one the issue, we felt that upgrading the current LVM2 package in our repository will be the best approach.
>>> >> > As part of that, we have updated the respective package from  2.02.176 to 2.02.180. We have verified the same and booted x86_64 hardware without any issues.
>>> >> >
>>> >> > But while trying to boot mips64 hardware we have started observing the below issue.  Providing the snippet of the log,
>>> >> >
>>> >> > # executing command: vgchange -an
>>> >> > (status, output): (0,   WARNING: Failed to connect to lvmetad. Falling back to device scanning.)
>>> >> >   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>> >> >
>>> >> > Attached the detailed log for reference. There is no other change included other than the LVM2 update.
>>> >> >
>>> >> > LVM2 Version: 2.02.176
>>> >> > Updated LVM2 version: 2.02.180
>>> >> >
>>> >> > Please share inputs on why this issue is being observed with .180 version?
>>> >> > Please let me know if i can share any other information.
>>> >> >
>>> >> > 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/
>>> >>
>>> >> _______________________________________________
>>> >> 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 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 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 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/

^ permalink raw reply	[flat|nested] 8+ messages in thread
end of thread, other threads:[~2020-09-17 16:26 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-10 13:53 [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180 KrishnaMurali Chennuboina
2020-09-14 14:58 ` Roger Heflin
2020-09-14 15:19   ` KrishnaMurali Chennuboina
2020-09-15 11:05     ` Roger Heflin
2020-09-15 12:58       ` KrishnaMurali Chennuboina
2020-09-15 17:01         ` KrishnaMurali Chennuboina
2020-09-17 16:26           ` Roger Heflin
2020-09-15 18:46       ` Zdenek Kabelac

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