From: svetljo <galia@st-peter.stw.uni-erlangen.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvcreate segfault in vg_setup_pointers_for_snapshots
Date: Wed, 03 Oct 2001 21:12:40 +0200 [thread overview]
Message-ID: <3BBB6328.8020504@st-peter.stw.uni-erlangen.de> (raw)
In-Reply-To: Pine.LNX.4.33.0110031956510.16480-100000@dunlop.dub.ie.alphyra.com
some my thoughts:
you can not expect that lvm tools will work in case the kernel code is
different version
every time you change the tools you should also patch the kernel
in the case with 0.9.1beta7,
i didn't know that it is possible to use any lvm code prior lvm-1.0.1rc1
( the min -max changes in linus's 2.4.9 -- the reason for lvm-1.0.1rc1)
and thats making me to think that you didn't patch the kernel,
the plain kernel comes with lvm-0.9.1beta2
so see again the begining
Paul Jakma wrote:
>and some more info:
>
>lvm 1.0.1rc3 compiled with RH gcc 2.96-97 running on the kernel
>described below (ie 0.9.1b7 kernel) also segfaults in the exact same
>way.
>
>regards,
>
>--paulj
>
>On Wed, 3 Oct 2001, Paul Jakma wrote:
>
>>doh...
>>
>>this is 0.9.1beta7, on stock kernel 2.4.9 + LVM 0.9.1beta7 + ext3 + NFS fixups
>>
>>On Wed, 3 Oct 2001, Paul Jakma wrote:
>>
>>>hi,
>>>
>>>running lvcreate consistently segfaults on me, eg:
>>>
>>> /lib/lvm-iop10/lvcreate -L 600M -n var_cache_lv Main_VG
>>>
>>>
>>>#0 0x4004500b in vg_setup_pointers_for_snapshots (vg=0x8058038)
>>> at vg_setup_pointers_for_snapshots.c:37
>>>37 if ( lv_chain_ptr->lv_access & LV_SNAPSHOT_ORG) {
>>>(gdb) bt
>>>#0 0x4004500b in vg_setup_pointers_for_snapshots (vg=0x8058038)
>>> at vg_setup_pointers_for_snapshots.c:37
>>>#1 0x40045d0d in vg_status_with_pv_and_lv (vg_name=0xbffffbe3 "Main_VG",
>>> vg=0xbffff254) at vg_status_with_pv_and_lv.c:63
>>>#2 0x0804abbd in strcpy ()
>>>#3 0x400767c7 in __libc_start_main (main=0x8049370 <strcpy+272>, argc=6,
>>> ubp_av=0xbffffaa4, init=0x8048ea8 <_init>, fini=0x804beb0 <_fini>,
>>> rtld_fini=0x4000db74 <_dl_fini>, stack_end=0xbffffa9c)
>>> at ../sysdeps/generic/libc-start.c:129
>>>(gdb) print *vg
>>>$3 = {vg_name = "Main_VG", '\000' <repeats 120 times>, vg_number = 0,
>>> vg_access = 3, vg_status = 5, lv_max = 256, lv_cur = 6, lv_open = 5,
>>> pv_max = 256, pv_cur = 2, pv_act = 2, dummy = 0, vgda = 0, pe_size = 8192,
>>> pe_total = 3690, pe_allocated = 849, pvg_total = 0, proc = 0x0, pv = {
>>> 0xc7c83800, 0xc7c83a00, 0x0 <repeats 255 times>}, lv = {0xc7c83c00,
>>> 0xc7c83e00, 0xc65e3000, 0xc65e3200, 0xc65e3400, 0xc65e3600,
>>> 0x0 <repeats 251 times>}, vg_uuid = "Main_VG", '\000' <repeats 25 times>,
>>> dummy1 = "\000\000\000`���`���`���", '\000' <repeats 184 times>}
>>>(gdb) print *lv_chain_ptr
>>>Cannot access memory at address 0xc7c83c00
>>>
>>>and boom...
>>>
>>>any fixes for this? i've tried compiling with both RH's compat-egcs
>>>and gcc-2.96-97 compilers, same result each time.
>>>
>>>ta,
>>>
>>>--paulj
>>>
>>--paulj
>>
>>
>>_______________________________________________
>>linux-lvm mailing list
>>linux-lvm@sistina.com
>>http://lists.sistina.com/mailman/listinfo/linux-lvm
>>read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>>
>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
next prev parent reply other threads:[~2001-10-03 19:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 15:30 [linux-lvm] lvcreate segfault in vg_setup_pointers_for_snapshots Paul Jakma
2001-10-03 18:22 ` Paul Jakma
2001-10-03 19:00 ` Paul Jakma
2001-10-03 19:12 ` svetljo [this message]
2001-10-03 19:30 ` Andreas Dilger
2001-10-03 19:40 ` svetljo
2001-10-03 19:52 ` Paul Jakma
2001-10-03 20:44 ` svetljo
2001-10-03 19:56 ` Paul Jakma
2001-10-04 0:45 ` Paul Jakma
2001-10-04 2:54 ` [linux-lvm] What have I done!? Jason A. Lixfeld
2001-10-04 3:06 ` Jason A. Lixfeld
2001-10-04 5:44 ` idsfa
2001-10-04 11:00 ` Jason A. Lixfeld
2001-10-04 11:24 ` Jason A. Lixfeld
2001-10-04 17:33 ` Andreas Dilger
2001-10-04 17:57 ` Steven Lembark
2001-10-05 7:05 ` Heinz J . Mauelshagen
2001-10-04 3:28 ` [linux-lvm] lvcreate segfault in vg_setup_pointers_for_snapshots Jason A. Lixfeld
2001-10-04 3:33 ` Andreas Dilger
2001-10-04 3:46 ` Jason A. Lixfeld
2001-10-04 6:04 ` Andreas Dilger
2001-10-04 7:05 ` Sean Burford
2001-10-04 10:31 ` Paul Jakma
2001-10-04 11:05 ` Joe Thornber
2001-10-04 14:51 ` Paul Jakma
2001-10-04 11:38 ` Jason A. Lixfeld
2001-10-04 14:01 ` Jason A. Lixfeld
2001-10-04 14:23 ` Jason A. Lixfeld
2001-10-04 15:57 ` Jason A. Lixfeld
2001-10-04 20:12 ` Goetz Bock
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=3BBB6328.8020504@st-peter.stw.uni-erlangen.de \
--to=galia@st-peter.stw.uni-erlangen.de \
--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;
as well as URLs for NNTP newsgroup(s).