From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alasdair G Kergon Subject: Re: [PATCH 16/24] dm cache: log error message if dm_kcopyd_copy() fails Date: Fri, 8 Nov 2013 13:33:11 +0000 Message-ID: <20131108133311.GA3876@agk-dp.fab.redhat.com> References: <1382639437-27007-1-git-send-email-snitzer@redhat.com> <1382639437-27007-17-git-send-email-snitzer@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: <1382639437-27007-17-git-send-email-snitzer@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: Mike Snitzer Cc: Morgan Mears , Heinz Mauelshagen , dm-devel@redhat.com, Joe Thornber List-Id: dm-devel.ids On Thu, Oct 24, 2013 at 02:30:29PM -0400, Mike Snitzer wrote: > A migration failure should be logged (albeit limited). Does this *really* add anything useful? migration_failure() already always logs a message, so you'll now get two (throttled) messages instead of one every time. Would it be better to log not just the type of failure but also some details about the data block location too? And if you really need to know "issuing migration failed" then why not just add the string to the existing log message? Alasdair