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 09:09:01 2003 [thread overview]
Message-ID: <20031027160955.M848@sistina.com> (raw)
In-Reply-To: <3F9D327C.6020102@elitedvb.net>; from tmbinc@elitedvb.net on Mon, Oct 27, 2003 at 03:58:04PM +0100
On Mon, Oct 27, 2003 at 03:58:04PM +0100, Felix Domke wrote:
> Hi,
>
> >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.
> >
> >
> Where exactly is the LV information passed to the kernel? is it
> "LV_CREATE"?
Yes.
>
> The kernel seems to don't know the LV, the LV_STATUS_BYINDEX on the
> "/dev/fast/group" returns "No such device or address" (ENXIO) for each
> index, including 0, which should be the LV in question.
>
> It looks as "lvm_do_lv_status_byindex" in the kernel returns -ENXIO
> because vg_ptr->lv[lv_status_byindex_req.lv_index] is zero. Where is the
> point where this array is written? I only found LV_CREATE, but that's
> only called in vgimport, vgmerge and lvcreate, so it looks as there is
See lvm_do_vg_create() and lvm_do_lv_create() functions in the driver.
> another place.
>
>
> Can you point me in the direction?
>
>
> 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 9: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
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 [this message]
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=20031027160955.M848@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.