All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Segmentation fault in vgscan
Date: Fri Aug 22 08:01:01 2003	[thread overview]
Message-ID: <20030822145330.J8426@sistina.com> (raw)
In-Reply-To: <E19qASV-0007ji-AX@server2.hostpoint.ch>; from markus@markus.org on Fri, Aug 22, 2003 at 01:51:44PM +0200

On Fri, Aug 22, 2003 at 01:51:44PM +0200, Markus Baertschi wrote:
> 
> Heinz,
> 
> It looks like I'll be able to test stuff sometimes next week.

Please do so.

> Is these anything I can do to help pinpoint the problem ?

Let's wait if it is reproducable with 1.0.7.

Can you make sure that you generate the software from scratch
and fo a full install which makes sure that you really use the 1.0.7
lib as well (configure ; make ; make install) ?

> 
> Markus
> 
> On Fri, 22 Aug 2003 13:01:45 +0200, Heinz J . Mauelshagen wrote:
> 
> >On Fri, Aug 22, 2003 at 12:50:36PM +0200, Markus Baertschi wrote:
> >> 
> >> Heinz,
> >> 
> >> I'm pretty sure I've tested with 1.0.7. Look at the lines
> 
> >Well, I derived the line numbers from the respective sources.
> 
> >> 
> >> >> lblsapq00:~ # gdb ./LVM/1.0.7/tools/vgscan
> >>   ...
> >> >> (gdb) run
> >> >> Starting program: /root/./LVM/1.0.7/tools/vgscan
> >> 
> >> The other problem is that this is at a customer site on
> >> production machines. I can test the next time I'm there
> >> and got machine time to do some testing. This will happen
> >> as soon as the SAN support guys come back to me to solve
> >> the undelying problem (disks visible twice).
> 
> >Ok.
> 
> >Regards,
> >Heinz    -- The LVM Guy --
> 
> 
> --
>   Markus Baertschi             Phone: ++41 (21) 807 1677
>   Bas du Rossé 14b             Fax  : ++41 (21) 807 1678
>   CH-1163, Etoy                Email: markus@markus.org
>   Switzerland                  Homepage: www.markus.org
> 
> 
> 
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-08-22  8:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21 15:09 [linux-lvm] Segmentation fault in vgscan Markus Baertschi
2003-08-22  5:34 ` Heinz J . Mauelshagen
2003-08-22  5:52   ` Markus Baertschi
2003-08-22  6:09     ` Heinz J . Mauelshagen
2003-08-22  6:53       ` Markus Baertschi
2003-08-22  8:01         ` Heinz J . Mauelshagen [this message]
2003-09-10  7:11           ` Markus Baertschi

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=20030822145330.J8426@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.