linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Pasha Z <free.lan.c2.718r@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvm hangup on snapshot overflow
Date: Sat, 13 Aug 2011 23:53:30 +0100	[thread overview]
Message-ID: <20110813225330.GA6019@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <CAA-yEOLgSqD7N5C773M=54CmVy8=aYybkw1AWOhWmZgc+ET68Q@mail.gmail.com>

On Fri, Aug 12, 2011 at 07:05:31PM +0300, Pasha Z wrote:
> lvconvert device-mapper: suspend ioctl failed: Input/output error
> lvconvert Unable to suspend VG-sn_x (252:3)
> lvconvert Failed to suspend origin lv
 
What exactly are you trying to do with lvconvert rather than lvcreate?

Never let snapshots fill up - use dmeventd instead and intervene in
a controlled way before they are full.

The lvconvert -s man page is too subtle and needs improving.

Alasdair

  reply	other threads:[~2011-08-13 22:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 16:05 [linux-lvm] lvm hangup on snapshot overflow Pasha Z
2011-08-13 22:53 ` Alasdair G Kergon [this message]
2011-08-16  8:40   ` Pasha Z

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=20110813225330.GA6019@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=free.lan.c2.718r@gmail.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 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).