From: Chris Mason <clm@fb.com>
To: "Oliver O." <oliver.o456i@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Solved, false alarm - Re: File changing in snapshot
Date: Fri, 18 Apr 2014 13:08:07 -0400 [thread overview]
Message-ID: <53515BF7.4020507@fb.com> (raw)
In-Reply-To: <535149D4.3090305@gmail.com>
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
prev parent reply other threads:[~2014-04-18 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 15:39 File changing in snapshot Oliver O.
2014-04-17 15:56 ` Chris Mason
2014-04-17 16:11 ` Oliver O.
2014-04-17 21:29 ` Oliver O.
2014-04-18 15:50 ` Solved, false alarm - " Oliver O.
2014-04-18 17:08 ` Chris Mason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53515BF7.4020507@fb.com \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=oliver.o456i@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).