From: Paul Warren <pdw@ex-parrot.com>
To: oxlug@lists.oxlug.org, linux-lvm@redhat.com
Subject: [linux-lvm] Re: [OxLUG] LVM2 problems
Date: Fri, 15 Oct 2004 20:18:22 +0100 [thread overview]
Message-ID: <20041015201822.B29778@sphinx.mythic-beasts.com> (raw)
In-Reply-To: <20041015185452.GG565@scooby.ox.compsoc.net>; from agk@redhat.com on Fri, Oct 15, 2004 at 07:54:52PM +0100
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
next prev parent reply other threads:[~2004-10-15 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041015192848.O30562@sphinx.mythic-beasts.com>
2004-10-15 18:54 ` [linux-lvm] Re: [OxLUG] LVM2 problems Alasdair G Kergon
2004-10-15 19:18 ` Paul Warren [this message]
2004-10-15 20:50 ` Paul Warren
2004-10-15 21:09 ` Alasdair G Kergon
2004-10-15 21:18 ` Paul Warren
2004-10-15 21:49 ` Alasdair G Kergon
2004-10-18 0:43 ` Jon Masters
2004-10-15 22:57 Kai Leibrandt
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=20041015201822.B29778@sphinx.mythic-beasts.com \
--to=pdw@ex-parrot.com \
--cc=linux-lvm@redhat.com \
--cc=oxlug@lists.oxlug.org \
/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