All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Nichols" <tnichols@Is-design.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] lvcreate seg faults in 1.0.1-r4
Date: Sat Nov 24 21:08:01 2001	[thread overview]
Message-ID: <002301c1755e$964da0d0$1a00000a@isdesign.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3045 bytes --]

I am having trouble getting lvcreate to work.  I've been able to create the PV and VG, but lvcreate always core dumps with a seg fault.   I've confirmed that I have the same code level in the kernel and tools (1.0.1-rc4).  I've tried compiling the tools with gcc (v2.96) and egcs (v2.91.66), but both fail.  I'm running a 2.4.14 kernel, lvm as a module, and glibc-2.2.4-19.  
  The problem seems to be with a corrupt lvol name from what I see in the gdb output I've attached.

 Any help would be great.

 Tim

[root@monolith /root]# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-85)

[root@monolith /root]# egcs -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)

[root@monolith /root]# cat /proc/lvm/global
LVM module LVM version 1.0.1-rc4(03/10/2001)

Total:  1 VG  1 PV  0 LVs (0 LVs open)
Global: 3175 bytes malloced   IOP version: 10   2:05:33 active

VG:  vg00  [1 PV, 0 LV/0 open]  PE Size: 4096 KB
  Usage [KB/PE]: 6635520 /1620 total  0 /0 used  6635520 /1620 free
  PV:  [AA] hdf1                   6635520 /1620           0 /0        6635520 /
1620
    LVs: none

[root@monolith /root]# lvcreate -L 1500 -n lvol1 vg00
Segmentation fault (core dumped)

[root@monolith /root]# lvcreate -L1500 -nlvol1 vg00
Segmentation fault (core dumped)

[root@monolith /root]# gdb lvcreate
GNU gdb 5.0rh-5 Red Hat Linux 7.1
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
(no debugging symbols found)...
(gdb) run -L1500 -nlvol1 vg00
Starting program: /sbin/lvcreate -L1500 -nlvol1 vg00

Program received signal SIGSEGV, Segmentation fault.
lv_create (vg=0x4, lv=0xbffff9f4,
    lv_name=0xbffffa08 "6ûÿ¿@ûÿ¿fûÿ¿{ûÿ¿\223ûÿ¿µûÿ¿Ôûÿ¿àûÿ¿êûÿ¿­ýÿ¿Ìýÿ¿æýÿ¿ûýÿ¿\
022þÿ¿\035þÿ¿Gþÿ¿Tþÿ¿\\þÿ¿lþÿ¿zþÿ¿\210þÿ¿\231þÿ¿§þÿ¿Éþÿ¿âþÿ¿íþÿ¿øþÿ¿+ÿÿ¿Úÿÿ¿")
    at lv_create_remove.c:42
42      int lv_create ( vg_t *vg, lv_t *lv, char *lv_name) {
(gdb) where
#0  lv_create (vg=0x4, lv=0xbffff9f4,
    lv_name=0xbffffa08 "6ûÿ¿@ûÿ¿fûÿ¿{ûÿ¿\223ûÿ¿µûÿ¿Ôûÿ¿àûÿ¿êûÿ¿­ýÿ¿Ìýÿ¿æýÿ¿ûýÿ¿\
022þÿ¿\035þÿ¿Gþÿ¿Tþÿ¿\\þÿ¿lþÿ¿zþÿ¿\210þÿ¿\231þÿ¿§þÿ¿Éþÿ¿âþÿ¿íþÿ¿øþÿ¿+ÿÿ¿Úÿÿ¿")
    at lv_create_remove.c:42
#1  0x0804b03d in strcpy ()
#2  0x40074627 in __libc_start_main (main=0x8049390 <strcpy+384>, argc=4,
    ubp_av=0xbffff9f4, init=0x8048e88 <_init>, fini=0x804b4d0 <_fini>,
    rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffff9ec)
    at ../sysdeps/generic/libc-start.c:129
(gdb) quit
The program is running.  Exit anyway? (y or n) y

[root@monolith /root]# uname -a
Linux monolith 2.4.14 #49 Sat Nov 24 00:27:41 PST 2001 i686 unknown

[-- Attachment #2: Type: text/html, Size: 5023 bytes --]

             reply	other threads:[~2001-11-24 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24 21:08 Tim Nichols [this message]
2001-11-25 12:10 ` [linux-lvm] lvcreate seg faults in 1.0.1-r4 Nils Juergens
2001-11-25 16:03   ` Tim Nichols
2001-11-26 12:37 ` Francis SOUYRI

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='002301c1755e$964da0d0$1a00000a@isdesign.com' \
    --to=tnichols@is-design.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.