All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart D Gathman <stuart@bmsi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Snapshot causing segault
Date: Thu, 03 Jan 2013 15:04:35 -0500	[thread overview]
Message-ID: <50E5E453.6080409@bmsi.com> (raw)
In-Reply-To: <50E55AFD.1040807@redhat.com>

On 01/03/2013 05:18 AM, Zdenek Kabelac expounded in part:
>
>> So my question is: is creating the snapshot volume with a size larger 
>> than the
>> target volume inducing segfaults randomly or could there be another 
>> problem
>> lurking? If these weren't production machines I would normally just 
>> go with a
>> size smaller than the target but I really need to be sure what 
>> exactly is
>> causing the segfaults.
>>
>> Any help would be appreciated.
>
>
> Any special reason to use lvm2 from the year 2006 in the year 2013 ?
> There is no big point in fixing some particular bugs any many years 
> obsoleted source code.
>
> Can you try to use/rebuild more recent version?
Upgrading production systems can be expensive - hence the value of paid 
long term support contracts.  I don't think he is asking to fix it - 
just to confirm that it is an LVM bug, which could make upgrading more 
attractive, or make the workaround (of ensuring snapshot size <= source 
size) acceptable.

  parent reply	other threads:[~2013-01-03 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-31 18:50 [linux-lvm] Snapshot causing segault Tyler Gates
2013-01-03 10:18 ` Zdenek Kabelac
2013-01-03 13:25   ` Tyler Gates
2013-01-03 20:04   ` Stuart D Gathman [this message]
2013-01-04 11:23 ` Milan Broz
2013-01-04 14:50   ` Tyler Gates

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=50E5E453.6080409@bmsi.com \
    --to=stuart@bmsi.com \
    --cc=linux-lvm@redhat.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.