From: "Oliver O." <oliver.o456i@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: File changing in snapshot
Date: Thu, 17 Apr 2014 17:39:45 +0200 [thread overview]
Message-ID: <534FF5C1.8070404@gmail.com> (raw)
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?
Sequence of events:
1. A (writable) snapshot @home-2014-04-16 is taken on a @home subvolume
mounted at /home.
2. The current subvolume (@home) is used (via /home) for continued write
access, no writes are supposed to occur on the snapshot.
3. The snapshot @home-2014-04-16 is backed up (using rdiff-backup) to a
different disk.
4. As the backup is compared to the snapshot @home-2014-04-16, one file
differs.
Further analysis:
The file in @home-2014-04-16 changed its contents (but not mtime or
other metadata) after being backup up from that snapshot. 5 bytes differ.
The previous snapshot @home-2014-04-10 contains the file in its original
form, which is identical to the backup just taken from @home-2014-04-16.
The file change appears identically
- on the last snapshot @home-2014-04-16 and
- on the current subvolume used for writing (@home).
btrfs scrub reports 0 errors.
At the time the snapshot @home-2014-04-16 was taken, the file (an Excel
file) was probably accessed through Samba, which supposedly uses kernel
oplocks (if that makes a difference).
Versions:
- Kernel 3.11.0-19-generic (Ubuntu 13.10)
- btrfs-tools 0.19+20130705-1
- Samba 3.6.18
Any ideas?
next reply other threads:[~2014-04-17 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 15:39 Oliver O. [this message]
2014-04-17 15:56 ` File changing in snapshot 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
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=534FF5C1.8070404@gmail.com \
--to=oliver.o456i@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.