On Thu, 14 Feb 2013, Chris Murphy wrote:
On Feb 14, 2013, at 8:50 PM, Fredrik Tolf <fred...@dolda2000.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
