diff options
author | Sage Weil <sage@newdream.net> | 2010-03-15 17:27:13 +0000 |
---|---|---|
committer | Chris Mason <chris.mason@oracle.com> | 2010-04-05 14:42:01 -0400 |
commit | 6bdb72ded1e281cd8844918c39d00cdd0e59f655 (patch) | |
tree | 39c25c85ddb1c2eecf7977e7e21a95f1c95ec21f /fs/Kconfig | |
parent | b5cb160084fad438c513d0952849e597ffe9e3d9 (diff) | |
download | kernel_samsung_crespo-6bdb72ded1e281cd8844918c39d00cdd0e59f655.zip kernel_samsung_crespo-6bdb72ded1e281cd8844918c39d00cdd0e59f655.tar.gz kernel_samsung_crespo-6bdb72ded1e281cd8844918c39d00cdd0e59f655.tar.bz2 |
Btrfs: create snapshot references in same commit as snapshot
This creates the reference to a new snapshot in the same commit as the
snapshot itself. This avoids the need for a second commit in order for a
snapshot to be persistent, and also avoids the problem of "leaking" a
new snapshot tree root if the host crashes before the second commit takes
place.
It is not at all clear to me why it wasn't always done this way. If there
is still a reason for the two-stage {create,finish}_pending_snapshots()
approach I'm missing something! :)
I've been running this for a couple weeks under pretty heavy usage (a few
snapshots per minute) without obvious problems.
Signed-off-by: Sage Weil <sage@newdream.net>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/Kconfig')
0 files changed, 0 insertions, 0 deletions