Bug#269383: kernel-image-2.4.27-1-686: Problem with devicemapper.

["alister.winfield" <alister.winfield@uk.easynet.net>]

Package: kernel-image-2.4.27-1-686-smp
Version: 2.4.27-1
Severity: normal
File: kernel-image-2.4.27-1-686

Sadly I don't have time to track down the problem much more but I have
created a bunch of lvm2 devices (so really just devicemapper devices).
These happen to be very close to the max size in a 2.4 kernel if it makes
any difference an example is:

  --- Logical volume ---
  LV Name                /dev/backup/backup09
  VG Name                backup
  LV UUID                tqr8VD-n1tc-tXNa-pycP-9wwh-giVj-blLtZP
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                1.95 TB
  Current LE             512000
  Segments               3
  Allocation             inherit
  Read ahead sectors     0
  Block device           254:9

But... asking for the size using the ioctl BLKGETSIZE64 (shifting to show 
number of 512 byte sectors) gives an insane  size.

For the above lv, from the devicemapper device.
36028796918300672 512 byte blocks (BLKGETSIZE64)

The underlying devices are reporting the right sizes eg
for sda1 I get : 2047998267 512 byte blocks (BLKGETSIZE64)
which matches what I am expecting. 

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27
Locale: LANG=en_GB, LC_CTYPE=en_GB

Versions of packages kernel-image-2.4.27-1-686-smp depends on:
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  initrd-tools                  0.1.74     tools to create initrd image for p
ii  modutils                      2.4.26-1   Linux module utilities

-- no debconf information