From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-btrfs-owner@vger.kernel.org>
Received: from mx0a-00082601.pphosted.com ([67.231.145.42]:18919 "EHLO
	mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1753862AbaDRRIB (ORCPT
	<rfc822;linux-btrfs@vger.kernel.org>);
	Fri, 18 Apr 2014 13:08:01 -0400
Message-ID: <53515BF7.4020507@fb.com>
Date: Fri, 18 Apr 2014 13:08:07 -0400
From: Chris Mason <clm@fb.com>
MIME-Version: 1.0
To: "Oliver O." <oliver.o456i@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Solved, false alarm - Re: File changing in snapshot
References: <534FF5C1.8070404@gmail.com> <534FF9B5.4010207@fb.com> <534FFD22.1060500@gmail.com> <535047AB.6030606@gmail.com> <535149D4.3090305@gmail.com>
In-Reply-To: <535149D4.3090305@gmail.com>
Content-Type: text/plain; charset="ISO-8859-15"; format=flowed
Sender: linux-btrfs-owner@vger.kernel.org
List-ID: <linux-btrfs.vger.kernel.org>



On 04/18/2014 11:50 AM, Oliver O. wrote:
> Am 17.04.2014 23:29, schrieb Oliver O.:

> Result: False alarm - this is definitely not a Btrfs problem. In this
> case snapshot behavior was as expected: atomic and stable.
>
> Sorry for any irritation.
>

But, mystery solved and documented for later generations ;)  Thanks for 
nailing it down and posting the result.

-chris