From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i9FJIXr18695 for ; Fri, 15 Oct 2004 15:18:33 -0400 Received: from sphinx.mythic-beasts.com (sphinx.mythic-beasts.com [212.69.37.6]) by mx3.redhat.com (8.12.11/8.12.10) with ESMTP id i9FJINr2014590 for ; Fri, 15 Oct 2004 15:18:23 -0400 Date: Fri, 15 Oct 2004 20:18:22 +0100 From: Paul Warren Message-ID: <20041015201822.B29778@sphinx.mythic-beasts.com> References: <20041015192848.O30562@sphinx.mythic-beasts.com> <20041015185452.GG565@scooby.ox.compsoc.net> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20041015185452.GG565@scooby.ox.compsoc.net>; from agk@redhat.com on Fri, Oct 15, 2004 at 07:54:52PM +0100 Sender: Paul Warren Subject: [linux-lvm] Re: [OxLUG] LVM2 problems Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: oxlug@lists.oxlug.org, linux-lvm@redhat.com On Fri, Oct 15, 2004 at 07:54:52PM +0100, Alasdair G Kergon wrote: > On Fri, Oct 15, 2004 at 07:28:48PM +0100, Paul Warren wrote: > > This should probably go on the linux-lvm mailing list, but the server > > seems to be down, > > Not as far as I know. > > http://sources.redhat.com/lvm2 -> linux-lvm@redhat.com Ah, thanks - I was trying: http://lists.sistina.com/mailman/listinfo/linux-lvm Which I took from the bottom of (what I thought was) a recent post. > > Our primary problem is that creating snapshots occassionally hangs the > > machine. > > Known issue now - unfortunately the fix involves a lot of coding and > other things have a higher priority at the moment. OK - I saw a previous post about this, but from that I wasn't sure that it (a) killed the machine and (b) affected ext3 partitions. > > /lib/lvm-200/lvm vgconvert -d -v -M1 mainvg > > Using volume group(s) on command line > > Finding volume group "mainvg" > > Archiving volume group "mainvg" metadata. > > Segmentation fault > > If it does it with the latest (2.00.25) version, > configure --enable-debug and send me the binary + core file > to investigate. OK - I'll give it a go and follow-up on linux-lvm. thanks for the help, Paul