[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-lvm] RE: LVM VG keeps disappearing



I'm still trying to figure out this problem.  When I run an "strace -f
-F vgscan" the only thing that looks odd to me is this:
open("/dev/vg01/group", O_RDONLY)       = 4
ioctl(4, 0xc004fe05, 0x800095b0)        = -1 ENXIO (No such device or
address)
close(4)                                = 0
open("/dev/vg01/group", O_RDONLY)       = 4
ioctl(4, 0xc004fe05, 0x800095b0)        = -1 ENXIO (No such device or
address)
close(4)                                = 0


Now, that device node does exist, so I don't understand what the error
means:
# ls -l /dev/vg01/group                                       
crw-r-----  1 root disk 109, 0 Feb 17 02:15 /dev/vg01/group 


When I compare the output to another system where LVM is working, I get
this:
open("/dev/vg01/group", O_RDONLY)       = 4
ioctl(4, 0xc004fe05, 0x406600)          = 0
close(4)                                = 0                  


Does this suggest anything to anyone?  Can anyone help me?  Thanks,

Mark Post

-----Original Message-----
From: Post, Mark K 
Sent: Tuesday, May 31, 2005 6:24 PM
To: 'linux-lvm redhat com'
Subject: LVM VG keeps disappearing


Twice now, I've had a VG "disappear" on me when I reboot my system.
These two instances were widely separated in time, with several reboots
in between.

When the system comes up vgscan runs, but I get this error:
vgscan -- reading all physical volumes (this may take a while...)

vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of
volume 
group "vg01" from physical volume(s)

vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created

vgscan -- WARNING: This program does not do a VGDA backup of your volume
group  

The first time this happened, I wound up just restoring all my logical
volumes from backup.  This time I would like to try to figure out: 1.
How to recover from this without restoring everything from backup. 2.
Why this happens so that a fix can be created.

This system is a slack/390 operating system, 64-bit, running a 2.4.26
kernel.

The LVM version I'm running is 1.0.8.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]