PVLink Failed - Corrupt file system

[D Heindel]

Last week we began having a problem with one of our disk drives. The below error was repeated every minute in syslog until the server was rebooted. Rebooting the server stopped the message from showing up, but the system still hangs whenever the disk is accessed. The volume group that the disk is a part of does not contain data we need, so I was trying to delete it and recreate it. When I try to remove the volume group in SAM it keeps hanging when trying to unmount the file system. Any ideas on how to fix the problem with the file system or how to delete the volume group? I have tried using fsck, but because I cannot unmount the file system it has not helped.

Jun 22 19:44:49 quadax-d vmunix:
Jun 22 19:44:49 quadax-d vmunix: SCSI: Read error -- dev: b 31 0x066000, errno:
126, resid: 1024,
Jun 22 19:44:49 quadax-d vmunix: blkno: 8, sectno: 16, offset: 8192, bcou
nt: 1024.
Jun 22 19:44:49 quadax-d vmunix: LVM: VG 64 0x010000: Lost quorum.
Jun 22 19:44:49 quadax-d vmunix: This may block configuration changes and I/Os.
In order to reestablish quorum at least 1 of the following PVs (represented by c
urrent link) must become available:
Jun 22 19:44:49 quadax-d vmunix: <31 0x066000>
Jun 22 19:44:49 quadax-d vmunix: LVM: VG 64 0x010000: PVLink 31 0x066000 Failed!
The PV is not accessible.
Jun 22 19:44:54 quadax-d vmunix: LVM: VG 64 0x010000: Reestablished quorum.
Jun 22 19:44:54 quadax-d vmunix: LVM: VG 64 0x010000: PVLink 31 0x066000 Recover

[Steven E. Protter]

Shalom,

The only conclusion I can come to is that the alternate link was either never working or both paths failed at the same time.

It is also possible that the LUN on the SAN was corrupted on the SAN. I'd check with the SAM admin on this.

The system sees it as a disk. It may act a little different than local disk, but in general, this is where I'd start.

SEP

[Tim Nelson]

I am suprised that after the reboot the filesystems(s) on that disk actually mounted as the disk is gone/bad.


1) manually attempt to umount on all filesystems associated with this VG.If busy message, run fuser on these mounted filesystems to see if there are processes with open files. shutdown those processes then umount and vgexport.


2) Boot to single user mode then vgexport the volume group.