summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/ctree.c
diff options
context:
space:
mode:
authorSage Weil <sage@newdream.net>2010-03-15 18:27:13 +0100
committerChris Mason <chris.mason@oracle.com>2010-04-05 20:42:01 +0200
commit6bdb72ded1e281cd8844918c39d00cdd0e59f655 (patch)
tree39c25c85ddb1c2eecf7977e7e21a95f1c95ec21f /fs/btrfs/ctree.c
parentBtrfs: fix small race with delalloc flushing waitqueue's (diff)
downloadlinux-6bdb72ded1e281cd8844918c39d00cdd0e59f655.tar.xz
linux-6bdb72ded1e281cd8844918c39d00cdd0e59f655.zip
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/btrfs/ctree.c')
0 files changed, 0 insertions, 0 deletions