From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: Re: [linux-lvm] Installing LVM on s/390 redhat 7.2 2.4.7-39
Date: Tue Jan 28 05:20:01 2003 [thread overview]
Message-ID: <20030128111907.GA880@tykepenguin.com> (raw)
In-Reply-To: <20030128110811.OREX14589.mta02-svc.ntlworld.com@[10.137.100.62]>
On Tue, Jan 28, 2003 at 11:08:11AM +0000, jrelist@ntlworld.com wrote:
>
> Peter
>
> Still get the problem with kernel 2.4.9-38. I took your advice and checked out the System.map and got this:
>
> 000315e8 T lock_kiovec
> 00031800 T unlock_kiovec
> 00050940 T brw_kiovec
> 00068688 T alloc_kiovec_sz
> 0006873c T free_kiovec_sz
> 001ca412 ? __kstrtab_alloc_kiovec_sz
> 001ca430 ? __kstrtab_free_kiovec_sz
> 001ca4a4 ? __kstrtab_lock_kiovec
> 001ca4be ? __kstrtab_unlock_kiovec
> 001ca4da ? __kstrtab_brw_kiovec
> 001d1d68 ? __ksymtab_alloc_kiovec_sz
> 001d1d70 ? __ksymtab_free_kiovec_sz
> 001d1d90 ? __ksymtab_lock_kiovec
> 001d1d98 ? __ksymtab_unlock_kiovec
> 001d1da0 ? __ksymtab_brw_kiovec
>
> Strikes me that it could be something (hopefully) as simple as amending labels in the appropriate lvm code - just got to suss out what needs changing now.
>
> Thanks for the advice so far
>
> John
This is quite an old problem (but then 2.4.9 is an old kernel I suppose!)
See:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0111.1/0815.html
patrick
next prev parent reply other threads:[~2003-01-28 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 5:09 Re: [linux-lvm] Installing LVM on s/390 redhat 7.2 2.4.7-39 jrelist
2003-01-28 5:20 ` Patrick Caulfield [this message]
2003-01-28 18:58 ` Peter A. Castro
-- strict thread matches above, loose matches on Subject: below --
2003-01-30 12:23 jrelist
2003-01-30 5:56 jrelist
2003-01-30 6:05 ` Patrick Caulfield
2003-01-30 11:04 ` Peter A. Castro
2003-01-29 4:31 jrelist
2003-01-27 7:05 jrelist
2003-01-23 16:00 jrelist
2003-01-23 18:35 ` Peter A. Castro
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=20030128111907.GA880@tykepenguin.com \
--to=caulfield@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox