[linux-lvm] Problems with dissapearing PV when mounting

[linux-lvm] Problems with dissapearing PV when mounting

[Johan Gardell]

Hi all!

I am having some troubles with mounting a vg consisting of two PVs.
After booting, the partition /dev/sdb5 does not pop up (but 1-3 does
and 4th is a swap). If i issue partprobe -s it does show up though.

partprobe shows:

/dev/sda: msdos partitions 1 2 3
/dev/sdb: msdos partitions 1 2 <5>
/dev/sdc: msdos partitions 1 3 2

I don't know what <> means but that is one of the PVs

If i, after issuing partprobe, use pvscan it shows:
  PV /dev/sdc2   VG Dreamhack   lvm2 [1,23 TiB / 0    free]
  PV /dev/sdb5   VG gardin      lvm2 [465,52 GiB / 0    free]
  PV /dev/sdd    VG gardin      lvm2 [465,76 GiB / 704,00 MiB free]
  Total: 3 [2,14 TiB] / in use: 3 [2,14 TiB] / in no VG: 0 [0   ]

vgscan:
  Reading all physical volumes.  This may take a while...
  Found volume group "Dreamhack" using metadata type lvm2
  Found volume group "gardin" using metadata type lvm2

But the problems appear when:
vgchange -ay gardin
  device-mapper: reload ioctl failed: Invalid argument
  device-mapper: reload ioctl failed: Invalid argument
  2 logical volume(s) in volume group "gardin" now active

Where dmesg shows:
[31936.135588] device-mapper: table: 254:1: linear: dm-linear: Device
lookup failed
[31936.135592] device-mapper: ioctl: error adding target to table
[31936.150572] device-mapper: table: 254:2: linear: dm-linear: Device
lookup failed
[31936.150576] device-mapper: ioctl: error adding target to table
[31940.024525] end_request: I/O error, dev fd0, sector 0

And trying to mount the vg:
mount /dev/mapper/gardin-root /mnt/tmp
  mount: you must specify the filesystem type

I have googled some but can't find much about this issue, does anyone
have any ideas how i can obtain the data stored on the disk? Because i
really need it..

I am running debian squeeze with a 2.6.30-2-686 kernel, the partitions
were originally created under debian lenny (don't know the kernel
version back then though)

lvm version shows:
  LVM version:     2.02.54(1) (2009-10-26)
  Library version: 1.02.39 (2009-10-26)
  Driver version:  4.14.0

Thanks in regards
//Johan

Re: [linux-lvm] Problems with dissapearing PV when mounting

[Stuart D. Gathman]

On Sun, 6 Dec 2009, Johan Gardell wrote:

> But the problems appear when:
> vgchange -ay gardin
>   device-mapper: reload ioctl failed: Invalid argument
>   device-mapper: reload ioctl failed: Invalid argument
>   2 logical volume(s) in volume group "gardin" now active
> 
> Where dmesg shows:
> [31936.135588] device-mapper: table: 254:1: linear: dm-linear: Device
> lookup failed
> [31936.135592] device-mapper: ioctl: error adding target to table
> [31936.150572] device-mapper: table: 254:2: linear: dm-linear: Device
> lookup failed
> [31936.150576] device-mapper: ioctl: error adding target to table
> [31940.024525] end_request: I/O error, dev fd0, sector 0

The fd0 error means you need to exclude /dev/fd0 from the vgscan in
/etc/lvm/lvm.conf (or wherever Debian puts it).  Start to worry
if you get I/O errors on sdb or sdc.

> And trying to mount the vg:
> mount /dev/mapper/gardin-root /mnt/tmp
>   mount: you must specify the filesystem type

You need to show us the output of 'lvs'.  (Even if it just spits out an error.)

Is there an LV named "root"?  I think so, since it would say "special device
does not exist" if not.  But what kind of filesystem did it have
on it?  Maybe it is not an auto-detected one, or you need to load
the filesystem driver.  Does mount report I/O error if it gets one
trying to identify the filesystem?

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.