linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: svetljo <galia@st-peter.stw.uni-erlangen.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] More Segfaults with LVM 1.0.1rc3
Date: Sun, 07 Oct 2001 14:30:17 +0200	[thread overview]
Message-ID: <3BC04AD9.9080300@st-peter.stw.uni-erlangen.de> (raw)
In-Reply-To: 3BBD6C17.8090405@st-peter.stw.uni-erlangen.de

>
> Heinz J . Mauelshagen wrote:
>
>> On Fri, Oct 05, 2001 at 09:25:56AM +0200, svetljo wrote:
>>
>>> is gcc-3.0.1 safe, or i should also use "-o0"
>>>
>>
>> Don't have a report for this :-(
>> Please try it.
>>
> it's seems to work
>
> xxscan xxdiplay lvcreate lvremove lvrename lvextend lvreduce work 
> without pb
> but i tried yesterday to install 2.4.11-pre2-xfs-cvs lvm-cvs
> and vgscan from the initrd segfaults , i can not boot to my LV's with it
> probbably it's some other trouble, i'll try with 2.4.11-pre3-xfs
> i think it's not relevant but all my VG's are over softRAIDs
>
it works with 2.4.11-pre4-xfs-cvs and lvm-cvs from today
i couldn't test vgcreate and vgremove .. ( because i have no spare PV's)
but the other tools work without complaining

  parent reply	other threads:[~2001-10-07 12:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04 20:33 [linux-lvm] More Segfaults with LVM 1.0.1rc3 Markus Dobel
2001-10-05  7:08 ` Heinz J . Mauelshagen
2001-10-05  7:25   ` svetljo
2001-10-05  7:57     ` Heinz J . Mauelshagen
2001-10-05  8:15       ` svetljo
2001-10-06 23:18         ` Nils Juergens
2001-10-08 10:02           ` Heinz J . Mauelshagen
2001-10-10 21:41             ` Nils Juergens
2001-10-07 12:30         ` svetljo [this message]
2001-10-08 10:03           ` Heinz J . Mauelshagen
2001-10-09  0:25             ` Paul Jakma
2001-10-09  0:40               ` Luca Berra
2001-10-09  7:42               ` Joe Thornber

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=3BC04AD9.9080300@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).