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: Mon Oct 27 05:00:02 2003 [thread overview]
Message-ID: <20031027120104.K848@sistina.com> (raw)
In-Reply-To: <3F9C0AC9.6050805@elitedvb.net>; from tmbinc@elitedvb.net on Sun, Oct 26, 2003 at 06:56:25PM +0100
On Sun, Oct 26, 2003 at 06:56:25PM +0100, Felix Domke wrote:
> Heinz J . Mauelshagen wrote:
>
> >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.
> >
> >
> Hi,
>
> i could setup external access to the machine, but be aware that it
> consists of a chroot'ed 64bit hacked-together debian, so compiling
> something with 64bit isn't any fun at all. The 32bit userspace however
> is fine.
>
> I tried to compile the lvmtools as 64bit, but the result didn't change.
> are there any points where i can put some debug printfs/printks in the
> sources to work out where it fails? I never looked at the LVM internals,
> so i don't know what happens where. Does the kernel space reads and
> parses the metadata? Or does the userspace parses it and passes it to
> the kernel?
User space parses and passes it via ioctls to the kernel.
Please look at lvm.h for the ioctls defined and the structures involved.
Grep the LVM1 library source in tools/lib/ for "ioctl" to get you started.
>
> 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/
--
Regards,
Heinz -- The LVM Guy --
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-10-27 5:00 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
2003-10-26 11:54 ` Felix Domke
2003-10-27 5:00 ` Heinz J . Mauelshagen [this message]
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=20031027120104.K848@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.