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 m41Kb7qH022974 for ; Thu, 1 May 2008 16:37:07 -0400 Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id m41Katsp002234 for ; Thu, 1 May 2008 16:36:55 -0400 Received: from [192.168.2.102] ([72.91.189.24]) by vms173005.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K0700IJYIBHAL47@vms173005.mailsrvcs.net> for linux-lvm@redhat.com; Thu, 01 May 2008 15:30:54 -0500 (CDT) Date: Thu, 01 May 2008 16:36:45 -0400 From: Gerry Reno Subject: Re: [linux-lvm] F7 will not boot after running backup w/snapshot In-reply-to: <481A2947.9070907@Media-Brokers.com> Message-id: <481A29DD.6040108@verizon.net> MIME-version: 1.0 Content-transfer-encoding: 7bit References: <4818F2FC.5050907@verizon.net> <20080501154800.GA5941@us.ibm.com> <481A08A7.5010305@verizon.net> <481A0E28.5030108@Media-Brokers.com> <481A1C09.7070508@verizon.net> <481A1D32.6020705@Media-Brokers.com> <481A1FAF.5050303@verizon.net> <481A221D.80209@Media-Brokers.com> <481A262C.7080908@verizon.net> <20080501202534.GU18935@agk.fab.redhat.com> <481A286E.80309@verizon.net> <481A2947.9070907@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 4:30 PM, Gerry Reno wrote: >>>> At least in the case where the snapshot is read-only (LVM1 default, >>>> LVM2 by config?), if the snapshot is lost, invalid, not removed >>>> from VG prior to reboot, when LVM comes back up it should see this >>>> and immediately know that it can just vgreduce VG --removemissing >>>> for the old snapshot. In the case of rw (no LVM1, LVM2 default), >>>> it should be a user choice and LVM should prompt the user at boot >>>> as to whether to remove this old snapshot so it can attempt to >>>> activate the VG. Unless the user knows that there were non-backup >>>> related lvm mods written during the snapshot (eg: pvmove) then the >>>> user will just answer yes and the system should boot. This is how >>>> LVM should operate in this scenario. > >>> If you want your system to do that, update your initrd/initscripts >>> accordingly to run the appropriate lvm2 commands to do that! > >> I can certainly do that. But I think this applies in the general case >> and should be included as standard behavior in LVM. This is a much >> more robust means of dealing with this scenario that having LVM just >> refuse to mount the volume when the only issue is a bad snapshot. > > Question... > > In Gerry's scenario here, if the snapshot volume had NOT been on a ram > disk, would he have had the problem he had or not? > Charles, Without knowing the exact cause of the hang there is no way to know if the ramdisk was at issue. I doubt it myself, I ran a whole series of backups last night using the ramdisk snapshot and everything went fine. Gerry