From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moltke.seatribe.se ([178.63.100.209]:42833 "EHLO moltke.seatribe.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932671Ab3BOD5J (ORCPT ); Thu, 14 Feb 2013 22:57:09 -0500 Date: Fri, 15 Feb 2013 04:56:55 +0100 (CET) From: Fredrik Tolf To: Chris Murphy cc: Hugo Mills , linux-btrfs@vger.kernel.org Subject: Re: Rebalancing RAID1 In-Reply-To: <0716DBBF-5B83-4211-A038-81C84621FCD5@colorremedies.com> Message-ID: References: <5EEA9264-5DCA-4A3F-B305-F3E64E9A3CC5@colorremedies.com> <17E4F30E-2945-44FE-A87F-0F475DFD794F@colorremedies.com> <2D5AAB44-9DA8-460D-9141-3544DE6C45D7@colorremedies.com> <20130214085925.GD28997@carfax.org.uk> <19ABBC76-F774-4225-87A4-73A4D546F53F@colorremedies.com> <0716DBBF-5B83-4211-A038-81C84621FCD5@colorremedies.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Thu, 14 Feb 2013, Chris Murphy wrote: > On Feb 14, 2013, at 8:50 PM, Fredrik Tolf wrote: > >> >> So it's either from btrfs, or from the buffer cache, and seeing as how it appears with other btrfs messages, I'd be willing to bet on the former. :) > > Unclear. Google searches reveal this identical error comes up in non-btrfs contexts. I'd like to think that if it's kernel-btrfs related that it would get tagged as kerne: blah btrfs: lost page blah. It appears to me that the bulk of the containing function has been copy-pasted from buffer.c, so that's probably why the messages are identical. As you could see from the source code I quoted, the message was, in fact, not prepended with "btrfs: ". -- Fredrik Tolf