All of lore.kernel.org
 help / color / mirror / Atom feed
From: Spelic <spelic@shiftmail.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Zdenek Kabelac <zkabelac@redhat.com>,
	linux-lvm@redhat.com
Subject: Re: DM / LVM hangs if snapshot present on kernel v3.0.3
Date: Mon, 20 Feb 2012 16:09:40 +0100	[thread overview]
Message-ID: <4F426234.1020704@shiftmail.org> (raw)
In-Reply-To: <20120220135103.GB27388@redhat.com>

On 02/20/12 14:51, Mike Snitzer wrote:
> I've never seen this. Which distro are you using?

Ubuntu 11.04  64-bit but with vanilla 3.0.3 kernel

Ubuntu's lvm:
# lvm version
   LVM version:     2.02.66(2) (2010-05-20)
   Library version: 1.02.48 (2010-05-20)

> The "Snapshot cow pairing for exception table handover failed" is the 
> error path most commonly associated with the snapshot-merge feature. 
> Are you using snapshot-merge for the root LV (e.g. lvconvert --merge 
> ...)? Mike 

Absolutely not, never merged a snapshot in my life, and also the root of 
the host was *not* on LVM.

Here is some more info:

Host machine had 2 PV, 2 VG (each of 1 PV), only one LV had only one 
snapshot, more specifically:

PV1 (a MD raid) --> VG1 --> 5 x LVs used for virtual machines disks; of 
these, only one LV had one snapshot. No other snapshots. None of these 
volumes were mounted on the host. This is where the problem happened.
PV2 (a MD raid) --> VG2 --> 1 x LV , I don't remember if this was 
mounted on the host at that time or was a disk for a virtual machine, 
but anyway was not the root filesystem of the host. No snapshots here.

Root filesystem of the host was definitely *not* on LVM.

Unfortunately the machine where it happened is a production machine and 
it's too dangerous to try to reproduce it there; this weekend I tried to 
reproduce it elsewhere but clearly it didn't happen. I had a stack trace 
of the DM hang but I lost it, stupid me...

WARNING: multiple messages have this Message-ID (diff)
From: Spelic <spelic@shiftmail.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Zdenek Kabelac <zkabelac@redhat.com>,
	linux-lvm@redhat.com
Subject: Re: [linux-lvm] DM / LVM hangs if snapshot present on kernel v3.0.3
Date: Mon, 20 Feb 2012 16:09:40 +0100	[thread overview]
Message-ID: <4F426234.1020704@shiftmail.org> (raw)
In-Reply-To: <20120220135103.GB27388@redhat.com>

On 02/20/12 14:51, Mike Snitzer wrote:
> I've never seen this. Which distro are you using?

Ubuntu 11.04  64-bit but with vanilla 3.0.3 kernel

Ubuntu's lvm:
# lvm version
   LVM version:     2.02.66(2) (2010-05-20)
   Library version: 1.02.48 (2010-05-20)

> The "Snapshot cow pairing for exception table handover failed" is the 
> error path most commonly associated with the snapshot-merge feature. 
> Are you using snapshot-merge for the root LV (e.g. lvconvert --merge 
> ...)? Mike 

Absolutely not, never merged a snapshot in my life, and also the root of 
the host was *not* on LVM.

Here is some more info:

Host machine had 2 PV, 2 VG (each of 1 PV), only one LV had only one 
snapshot, more specifically:

PV1 (a MD raid) --> VG1 --> 5 x LVs used for virtual machines disks; of 
these, only one LV had one snapshot. No other snapshots. None of these 
volumes were mounted on the host. This is where the problem happened.
PV2 (a MD raid) --> VG2 --> 1 x LV , I don't remember if this was 
mounted on the host at that time or was a disk for a virtual machine, 
but anyway was not the root filesystem of the host. No snapshots here.

Root filesystem of the host was definitely *not* on LVM.

Unfortunately the machine where it happened is a production machine and 
it's too dangerous to try to reproduce it there; this weekend I tried to 
reproduce it elsewhere but clearly it didn't happen. I had a stack trace 
of the DM hang but I lost it, stupid me...

  reply	other threads:[~2012-02-20 15:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19  2:27 DM / LVM hangs if snapshot present on kernel v3.0.3 Spelic
2012-02-19  2:27 ` [linux-lvm] " Spelic
2012-02-19 10:00 ` [linux-lvm] [dm-devel] " Zdenek Kabelac
2012-02-20 13:51 ` Mike Snitzer
2012-02-20 13:51   ` [linux-lvm] " Mike Snitzer
2012-02-20 15:09   ` Spelic [this message]
2012-02-20 15:09     ` Spelic
2012-02-20 17:17     ` Zdenek Kabelac
2012-02-20 17:17       ` [linux-lvm] " Zdenek Kabelac
2012-02-21 10:22       ` Spelic
2012-02-21 10:22         ` [linux-lvm] " Spelic
2012-02-21 11:08         ` Zdenek Kabelac

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=4F426234.1020704@shiftmail.org \
    --to=spelic@shiftmail.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=snitzer@redhat.com \
    --cc=zkabelac@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.