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.13.1/8.13.1) with ESMTP id m41JcCQV010352 for ; Thu, 1 May 2008 15:38:12 -0400 Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id m41Jbt3m025866 for ; Thu, 1 May 2008 15:37:55 -0400 Received: from [192.168.2.102] ([72.91.189.24]) by vms173003.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K0700D0LFQ6P6Z3@vms173003.mailsrvcs.net> for linux-lvm@redhat.com; Thu, 01 May 2008 14:34:55 -0500 (CDT) Date: Thu, 01 May 2008 15:37:45 -0400 From: Gerry Reno Subject: Re: [linux-lvm] F7 will not boot after running backup w/snapshot In-reply-to: <481A0E28.5030108@Media-Brokers.com> Message-id: <481A1C09.7070508@verizon.net> MIME-version: 1.0 Content-transfer-encoding: 7bit References: <4817C2FD.1010909@verizon.net> <4817D97D.8060805@verizon.net> <4817ECAF.4020806@verizon.net> <48187B91.4060901@verizon.net> <1c748a490804300809s304f7fdfx55aeb0fd9c6cc7ab@mail.gmail.com> <4818AB1C.9030809@verizon.net> <4818BA5D.6070501@Media-Brokers.com> <4818D59A.8020906@verizon.net> <4818E262.4070105@redhat.com> <4818F2FC.5050907@verizon.net> <20080501154800.GA5941@us.ibm.com> <481A08A7.5010305@verizon.net> <481A0E28.5030108@Media-Brokers.com> Reply-To: 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"; format="flowed" To: LVM general discussion and development Charles Marcus wrote: > On 5/1/2008 2:15 PM, Gerry Reno wrote: >> Why? What value is the old snapshot at this point? > > ? It holds (a copy of) > all of the changes to your original (snapshotted) volume, so I imagine > it would be pretty important to most people? > > I'm not really understanding all the inner-workings of LVM, but now I > can see why using a ram disk for an LVM snapshot might not be a very > good idea for this one reason - it won't survive a reboot... > >> You just had a system reboot in the middle of a snapshotted backup so >> all you need to do is get the system up, redo another snapshot and >> retake your backup. I'm not interested in the old snapshot. > > I would be... but thats just me... It's like yesterday's newspaper. Why do you need to keep it? Gerry