From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kristina Clair Subject: lvremove locked up Date: Mon, 28 Feb 2005 12:50:48 -0500 Message-ID: References: Reply-To: Kristina Clair , device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: LVM general discussion and development , dm-devel@redhat.com List-Id: dm-devel.ids 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j1SHosK16851 for ; Mon, 28 Feb 2005 12:50:54 -0500 Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx3.redhat.com (8.12.11/8.12.11) with ESMTP id j1SHonBO010320 for ; Mon, 28 Feb 2005 12:50:49 -0500 Received: by rproxy.gmail.com with SMTP id j1so915258rnf for ; Mon, 28 Feb 2005 09:50:48 -0800 (PST) Message-ID: Date: Mon, 28 Feb 2005 12:50:48 -0500 From: Kristina Clair In-Reply-To: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit References: Subject: [linux-lvm] lvremove locked up Reply-To: Kristina Clair , LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" To: LVM general discussion and development , dm-devel@redhat.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