From: Alasdair G Kergon Subject: Re: [PATCH 1/6] dm cache: cache shrinking support Date: Mon, 11 Nov 2013 23:03:49 +0000 Message-ID: <20131111230349.GF24324@agk-dp.fab.redhat.com> References: <1384190448-3861-1-git-send-email-snitzer@redhat.com> <1384190448-3861-2-git-send-email-snitzer@redhat.com> <20131111211934.GB24324@agk-dp.fab.redhat.com> <20131111213232.GA5099@redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20131111213232.GA5099@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: device-mapper development List-Id: dm-devel.ids > DMERR("unable to shrink cache due to dirty blocks"); Also, what is the process to recover from this error, given that you have already lost the end of the device and you cannot now resume the device without a preresume failure? Do the tools support retrieval of the dirty blocks from the portion of the device that you do still have? Alasdair