All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristina Clair <kclair@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	dm-devel@redhat.com
Subject: lvremove locked up
Date: Mon, 28 Feb 2005 12:50:48 -0500	[thread overview]
Message-ID: <dff3752705022809504cadf1fc@mail.gmail.com> (raw)
In-Reply-To: <dff3752705022809087fe560f3@mail.gmail.com>

Hi All,

Today I had a first:  I was using lvremove to remove a snapshot, and
lvremove locked up trying to suspend the filesystem.  Between the time
when I made the snapshot and when I ran lvremove, we copied about 87G
of data over to the drive.  Is it possible that that was just too much
change for snapshots to deal with?

Mostly what I'm concerned about is that we were using snapshots
successfully up to this point, albeit conservatively.   Should I
consider this a fluke due to this one-time addition of so much data,
or should I expect this to happen again now that the volume has so
much data on it?

Thanks,
Kristina

WARNING: multiple messages have this Message-ID (diff)
From: Kristina Clair <kclair@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	dm-devel@redhat.com
Subject: [linux-lvm] lvremove locked up
Date: Mon, 28 Feb 2005 12:50:48 -0500	[thread overview]
Message-ID: <dff3752705022809504cadf1fc@mail.gmail.com> (raw)
In-Reply-To: <dff3752705022809087fe560f3@mail.gmail.com>

Hi All,

Today I had a first:  I was using lvremove to remove a snapshot, and
lvremove locked up trying to suspend the filesystem.  Between the time
when I made the snapshot and when I ran lvremove, we copied about 87G
of data over to the drive.  Is it possible that that was just too much
change for snapshots to deal with?

Mostly what I'm concerned about is that we were using snapshots
successfully up to this point, albeit conservatively.   Should I
consider this a fluke due to this one-time addition of so much data,
or should I expect this to happen again now that the volume has so
much data on it?

Thanks,
Kristina

       reply	other threads:[~2005-02-28 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dff3752705022809087fe560f3@mail.gmail.com>
2005-02-28 17:50 ` Kristina Clair [this message]
2005-02-28 17:50   ` [linux-lvm] lvremove locked up Kristina Clair

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=dff3752705022809504cadf1fc@mail.gmail.com \
    --to=kclair@gmail.com \
    --cc=dm-devel@redhat.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.