From: "Oliver O." <oliver.o456i@gmail.com>
To: Chris Mason <clm@fb.com>, linux-btrfs@vger.kernel.org
Subject: Re: File changing in snapshot
Date: Thu, 17 Apr 2014 18:11:14 +0200 [thread overview]
Message-ID: <534FFD22.1060500@gmail.com> (raw)
In-Reply-To: <534FF9B5.4010207@fb.com>
Am 17.04.2014 17:56, schrieb Chris Mason:
> On 04/17/2014 11:39 AM, Oliver O. wrote:
>> I seem to have observed a file on a (writable) snapshot changing
>> although there were no writes occuring on the snapshot itself. This is
>> not supposed to happen, right?
>
> Was this a nodatacow file?
>
> -chris
No. Mount options:
/dev/sda2 on /home type btrfs (rw,noatime,nodiratime,subvol=@home)
next prev parent reply other threads:[~2014-04-17 16:11 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. [this message]
2014-04-17 21:29 ` Oliver O.
2014-04-18 15:50 ` Solved, false alarm - " Oliver O.
2014-04-18 17:08 ` Chris Mason
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=534FFD22.1060500@gmail.com \
--to=oliver.o456i@gmail.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
/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).