All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LV only detected when using "lvscan -D" on amd64 kernel
Date: Sat Oct 25 02:09:01 2003	[thread overview]
Message-ID: <20031025091006.I848@sistina.com> (raw)
In-Reply-To: <3F994F88.8030908@elitedvb.net>; from tmbinc@elitedvb.net on Fri, Oct 24, 2003 at 06:12:56PM +0200

Felix,

this definitely looks like a 64bit ioctl related problem.
I don't have the equipment to test here so help (is external access to
your machine possible ?) is needed.

Regards,
Heinz    -- The LVM Guy --


On Fri, Oct 24, 2003 at 06:12:56PM +0200, Felix Domke wrote:
> Hi,
> 
> i have an amd64-based machine, upgraded from a normal one. I'm using 
> debian, right now still the 32bit version (except for compiling the kernel).
> 
> I'm using
> Linux opt 2.4.22-bk38 #4 SMP Wed Oct 22 06:44:13 UTC 2003 x86_64 GNU/Linux
> 
> using
> # dmesg  | grep "LVM"
> LVM version 1.0.7(28/03/2003)
> 
> The LVM consists of 4 disks, two 40GB, one 20GB and one 120GB, gives a 
> total of roughly 220GB. All disks seem to work properly,
> pvscan gives
> # pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE   PV "/dev/hdg" of VG "fast" [115.03 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/hdf" of VG "fast" [19.16 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/hdc" of VG "fast" [38.16 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/hdd" of VG "fast" [38.16 GB / 0 free]
> pvscan -- total: 4 [210.54 GB] / in use: 4 [210.54 GB] / in no VG: 0 [0]
> 
> vgscan gives
> # vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found active volume group "fast"
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume 
> group
> 
> so everything looks fine. The logical volume worked fine with the old 
> kernel (2.4.20 or something like this, for ia32.).
> 
> but
> # lvscan
> lvscan -- no logical volumes found
> 
> and
> # vgdisplay
> --- Volume group ---
> VG Name               fast
> VG Access             read/write
> VG Status             available/resizable
> VG #                  0
> MAX LV                256
> Cur LV                0
> Open LV               0
> MAX LV Size           255.99 GB
> Max PV                256
> Cur PV                4
> Act PV                4
> VG Size               210.52 GB
> PE Size               4 MB
> Total PE              53893
> Alloc PE / Size       0 / 0
> Free  PE / Size       53893 / 210.52 GB
> VG UUID               NiBxzC-W5zF-Mb37-5ajN-ljE9-5k53-Fzc26O
> 
> So the logical volume seems to be gone :/
> 
> HOWEVER,
> 
> # lvscan -D
> lvscan -- reading all physical volumes (this may take a while...)
> lvscan -- inactive          "/dev/fast/lvol1" [210.52 GB]
> lvscan -- 1 logical volumes with 210.52 GB total in 1 volume group
> lvscan -- 1 inactive logical volumes
> 
> and
> 
> # vgdisplay -D
> --- Volume group ---
> VG Name               fast
> VG Access             read/write
> VG Status             NOT available/resizable
> VG #                  0
> MAX LV                256
> Cur LV                1
> Open LV               0
> MAX LV Size           255.99 GB
> Max PV                256
> Cur PV                4
> Act PV                4
> VG Size               210.52 GB
> PE Size               4 MB
> Total PE              53893
> Alloc PE / Size       53893 / 210.52 GB
> Free  PE / Size       0 / 0
> VG UUID               NiBxzC-W5zF-Mb37-5ajN-ljE9-5k53-Fzc26O
> 
> so i think there must be still some hope. Looks like the kernel LVM 
> stuff is somehow broken. Can this be a 64bit issue? Is there anything  i 
> could test/upgrade/whatever? Do you need more outputs?
> Or did i simply forget to do anything?
> 
> 
> thanks,
> Felix
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-10-25  2:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24 11:10 [linux-lvm] LV only detected when using "lvscan -D" on amd64 kernel Felix Domke
2003-10-25  2:09 ` Heinz J . Mauelshagen [this message]
2003-10-26 11:54   ` Felix Domke
2003-10-27  5:00     ` Heinz J . Mauelshagen
2003-10-27  8:55       ` Felix Domke
2003-10-27  9:09         ` Heinz J . Mauelshagen
2003-10-27  9:37           ` Felix Domke
2003-10-28  3:36             ` Heinz J . Mauelshagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031025091006.I848@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.