From: Michael Marxmeier <mike@msede.com>
To: linux-lvm@msede.com
Subject: [linux-lvm] reproducible segfault in vgscan
Date: Wed, 03 May 2000 22:44:11 +0200 [thread overview]
Message-ID: <39108F9B.16FC50E0@msede.com> (raw)
Forwarded message form Paul Jakma <paulj@itg.ie>
-------- Original Message --------
Date: Wed, 3 May 2000 20:03:41 +0100 (IST)
From: Paul Jakma <paulj@itg.ie>
Subject: reproducible segfault in vgscan
Message-ID: <Pine.LNX.4.21.0005031928440.907-100000@rossi.itg.ie>
MIME-Version: 1.0
i have a reproducible segfault with vgscan.
i had pvmove'd several lv's. Then i rebooted. since then, vgscan
segfaults
the first 3 times out of every 4 times i run it.
eg:
[root@rossi linux]# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "Main_VG"
Segmentation fault
[root@rossi linux]# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found inactive volume group "Main_VG"
Segmentation fault
[root@rossi linux]# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found inactive volume group "Main_VG"
Segmentation fault
[root@rossi linux]# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found inactive volume group "Main_VG"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: you may not have an actual VGDA backup of your
volume
group
this means i have to call vgscan 4 times in a row from my initscripts
before i can run vgchange.. :(
vgcfgrestore also has the same behaviour. :( segfault, segfault,
segfault, ok, segfault, segfault segfault ok.. etc..
System is 2.3.99-pre6-pre7.
I've looked at the BUGS page but i don't see this problem listed.
Further info available on request..
regards,
Paul Jakma.
next reply other threads:[~2000-05-03 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 20:44 Michael Marxmeier [this message]
2000-05-03 22:27 ` [linux-lvm] reproducible segfault in vgscan Heinz 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=39108F9B.16FC50E0@msede.com \
--to=mike@msede.com \
--cc=linux-lvm@msede.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.