[linux-lvm] Error with 2.5.50-dm-2; vanilla OK

[linux-lvm] Error with 2.5.50-dm-2; vanilla OK

[Richard Chan]

Hi, I'm getting an error with 2.5.50-dm2 but vanilla 2.5.50 is OK.

When I try lvm vgchange -ay I get the error messages

Dec  9 21:49:54 dyndns12 kernel: device-mapper: allocating minor 0.
Dec  9 21:49:54 dyndns12 kernel: device-mapper: device /dev/hdb7 too 
small for target
Dec  9 21:49:54 dyndns12 kernel: device-mapper: internal error adding 
target to table
Dec  9 21:49:54 dyndns12 kernel: device-mapper: destroying table

3 of 4 LVs in the VG are OK

If I use vanilla 2.5.50 the LVs are created OK

Dec  9 21:49:54 dyndns12 kernel: device-mapper: allocating minor 0.
Dec  9 21:49:54 dyndns12 kernel: device-mapper: allocating minor 1.
Dec  9 21:49:54 dyndns12 kernel: device-mapper: allocating minor 2.
Dec  9 21:49:54 dyndns12 kernel: device-mapper: allocating minor 3.

lvm version
  LVM version:     1.95.11-cvs (2002-11-18)
  Library version: 0.96.07-ioctl-cvs (2002-11-21)
  Driver version:  1.0.6

lvm vgdisplay vg00
 --- Volume group ---
  VG Name               vg00
  System ID             caesar1000557946
  Format                lvm1
  VG Access             read/write
  VG Status             resizable
  MAX LV                255
  Cur LV                4
  Open LV               2
  Max PV                255
  Cur PV                2
  Act PV                2
  VG Size               39.89GB
  PE Size               4.00MB
  Total PE              10212
  Alloc PE / Size       9920 / 38.75GB
  Free  PE / Size       292 / 1.14GB
  VG UUID               SsC7qF-Jb43-vh72-TctL-wlpU-iPvx-1Hr3hS

This is the LV that causes grief:
 
lvm lvdisplay vg00
  --- Logical volume ---
  LV Name                /dev/vg00/LVmisc
  VG Name                vg00
  LV UUID                000000-0000-0000-0000-0000-0000-000001
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                20.00GB
  Current LE             5120
  Segments               2
  Allocation             next free
  Read ahead sectors     120
  Block device           254:1

Re: [linux-lvm] Error with 2.5.50-dm-2; vanilla OK

[Joe Thornber]

On Mon, Dec 09, 2002 at 10:15:45PM +0800, Richard Chan wrote:
> Hi, I'm getting an error with 2.5.50-dm2 but vanilla 2.5.50 is OK.
> 
> When I try lvm vgchange -ay I get the error messages
> 
> Dec  9 21:49:54 dyndns12 kernel: device-mapper: allocating minor 0.
> Dec  9 21:49:54 dyndns12 kernel: device-mapper: device /dev/hdb7 too 
> small for target
> Dec  9 21:49:54 dyndns12 kernel: device-mapper: internal error adding 
> target to table
> Dec  9 21:49:54 dyndns12 kernel: device-mapper: destroying table
> 
> 3 of 4 LVs in the VG are OK

Weird, the patch that is causing you the problem will be:

http://people.sistina.com/~thornber/patches/2.5-stable/2.5.50/2.5.50-dm-2/00005.patch

Though it still looks sane to me.  Can you send me the lvm2 log from
this vgchange along with the size in sectors of hdb7 please ?

- Joe

[linux-lvm] Error with 2.5.50-dm-2; vanilla OK

[Richard Chan]

> Weird, the patch that is causing you the problem will be:
>
> http://people.sistina.com/~thornber/patches/2.5-stable/2.5.50/2.5.50-dm-2/00005.patch <http://people.sistina.com/%7Ethornber/patches/2.5-stable/2.5.50/2.5.50-dm-2/00005.patch>
>
> Though it still looks sane to me.  Can you send me the lvm2 log from
> this vgchange along with the size in sectors of hdb7 please ?
> 
> - Joe

Sure - here is more information about my system - the PVs as below
Disk /dev/hdb: 255 heads, 63 sectors, 7297 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdb1   *         1      1044   8385898+  a5  FreeBSD
/dev/hdb2          1045      7297  50227222+   f  Win95 Ext'd (LBA)
/dev/hdb5          1045      2088   8385898+   7  HPFS/NTFS
/dev/hdb6          2089      4699  20972826   8e  Linux LVM
/dev/hdb7          4700      7297  20868403+  8e  Linux LVM

lvm pvdisplay --verbose
    Scanning for physical volume names
  --- Physical volume ---
  PV Name               /dev/hdb6
  VG Name               vg00
  PV Size               20.00GB / not usable 5.28MB
  Allocatable           yes (but full)
  PE Size (KByte)       4096
  Total PE              5119
  Free PE               0
  Allocated PE          5119
  PV UUID               vuszz2-2qjg-ArUm-k1dV-GjHO-86ZM-HGYCZo

  --- Physical volume ---
  PV Name               /dev/hdb7
  VG Name               vg00
  PV Size               19.90GB / not usable 7.30MB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              5093
  Free PE               292
  Allocated PE          4801
  PV UUID               p3a5G3-HJjq-L9Gl-KGQN-Pi45-fBJT-RVE2ms


Output of lvm vgchange -ay --verbose
(BTW I just noticed an ioctl complaint - don't know what it means)

lvm vgchange -ay --verbose
 device-mapper ioctl cmd 2 failed: Invalid argument
  Couldn't load device 'vg00-LVmisc'.
    Finding all volume groups
    Finding volume group "vg00"
    3 logical volume(s) in volume group "vg00" already active
    Found volume group "vg00"
    Found volume group "vg00"
    Found volume group "vg00"
    Loading vg00-LVmisc
    Found volume group "vg00"
    Found volume group "vg00"
    Found volume group "vg00"
    Found volume group "vg00"
    Found volume group "vg00"
    Activated logical volumes in volume group "vg00"
  3 logical volume(s) in volume group "vg00" now active

device-mapper: allocating minor 0.
device-mapper: device /dev/hdb7 too small for target
device-mapper: internal error adding target to table
device-mapper: destroying table
device-mapper: allocating minor 1.
device-mapper: allocating minor 2.

There ought to be 4 LVs and minors; when the system is right I get

lvm lvscan
  ACTIVE            '/dev/vg00/LVhome' [10.00GB] next free
  ACTIVE            '/dev/vg00/LVmisc' [20.00GB] next free
  ACTIVE            '/dev/vg00/LVjfs' [8.00GB] next free
  ACTIVE            '/dev/vg00/LVswap' [768.00MB] next free


Thanks
Richard

Re: [linux-lvm] Error with 2.5.50-dm-2; vanilla OK

[Joe Thornber]

On Tue, Dec 10, 2002 at 02:21:38PM +0800, Richard Chan wrote:
> Sure - here is more information about my system

Can you mail me (rather than the list) the complete lvm2 log after
trying your vgchange -ay.  Look at /etc/lvm/lvm.conf to see where it
is.

- Joe

Re: [linux-lvm] Error with 2.5.50-dm-2; vanilla OK

[Alasdair G Kergon]

On Tue, Dec 10, 2002 at 09:38:27AM +0000, Joe Thornber wrote:
> Can you mail me (rather than the list) the complete lvm2 log after
> trying your vgchange -ay.  
e.g. run 'vgchange -ay -vvv' and send the full output;
  or edit the log section config file to capture the debug output
  (see doc/example.conf):
    level = 7
    overwrite = 1
    file = "/tmp/lvmlog"

Alasdair
-- 
agk@uk.sistina.com

Re: [linux-lvm] Error with 2.5.50-dm-2; vanilla OK

[Richard Chan]

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

I'd like to report that the problem I encountered with 2.5.50-dm-2 (
on LV not mounted, ioctl error) has been fixed in 2.5.51-dm-1. I can
now get all my LVs with it.

Thanks Joe, whatever you did works a charm.

Regards
Richard

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2106 bytes --]

Re: [linux-lvm] Error with 2.5.50-dm-2; vanilla OK

[Richard Chan]

AAACKK - I spoke too soon. This is with 00005.patch backed out.
If I use 00005.patch the same problem occurs.

activate/dev_manager.c:431   Loading vg00-LVmisc
activate/dev_manager.c:622   Adding target: 0 20963328 linear /dev/hdb6 
20980088
activate/dev_manager.c:622   Adding target: 20963328 20979712 linear 
/dev/hdb7 8
568
ioctl/libdevmapper.c:372   dm create vg00-LVmisc 
SsC7qFJb43vh72TctLwlpUiPvx1Hr3h
S00000000000000000000000000000001
ioctl/libdevmapper.c:375   device-mapper ioctl cmd 2 failed: Invalid 
argument
activate/dev_manager.c:471   Couldn't load device 'vg00-LVmisc'.



Richard Chan wrote:

> I'd like to report that the problem I encountered with 2.5.50-dm-2 (
> on LV not mounted, ioctl error) has been fixed in 2.5.51-dm-1. I can
> now get all my LVs with it.
>
> Thanks Joe, whatever you did works a charm.
>
> Regards
> Richard