From mboxrd@z Thu Jan 1 00:00:00 1970 From: Douglas McClendon Subject: Re: DM_snapshot_cow filesystem (dmsetup create snapshot) Date: Thu, 01 Dec 2011 14:21:56 -0600 Message-ID: <4ED7E1E4.1000603@filteredperception.org> References: <4EABE131.8010706@googlemail.com> <20111029204947.GU23336@agk-dp.fab.redhat.com> <4ED2DF0F.1070108@filteredperception.org> <4ED59040.50406@filteredperception.org> <20111130220259.GA7595@agk-dp.fab.redhat.com> <4ED6BD81.4090609@filteredperception.org> <20111201141236.GB7595@agk-dp.fab.redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111201141236.GB7595@agk-dp.fab.redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: dm-devel@redhat.com List-Id: dm-devel.ids correction- "go read-write-rootfs' below should have been "go read-only-rootfs" -dmc -------- I admit that would indeed solve the present use case of keeping the overlay device functionally usable. In fact, going with a brutal virtual-plug-pulling halt triggered by snapshot full would be fine. Though I'd rather at that instant have the system go read-write-rootfs so that I can still poke around somewhat, rather than the screen go black.