Commit 9bc574de authored by Josef Bacik's avatar Josef Bacik Committed by David Sterba
Browse files

btrfs: skip log replay on orphaned roots

My fsstress modifications coupled with generic/475 uncovered a failure
to mount and replay the log if we hit a orphaned root.  We do not want
to replay the log for an orphan root, but it's completely legitimate to
have an orphaned root with a log attached.  Fix this by simply skipping
replaying the log.  We still need to pin it's root node so that we do
not overwrite it while replaying other logs, as we re-read the log root
at every stage of the replay.

CC: # 4.4+
Reviewed-by: default avatarFilipe Manana <>
Signed-off-by: default avatarJosef Bacik <>
Signed-off-by: default avatarDavid Sterba <>
parent 714cd3e8
......@@ -6317,9 +6317,28 @@ again:
wc.replay_dest = btrfs_read_fs_root_no_name(fs_info, &tmp_key);
if (IS_ERR(wc.replay_dest)) {
ret = PTR_ERR(wc.replay_dest);
* We didn't find the subvol, likely because it was
* deleted. This is ok, simply skip this log and go to
* the next one.
* We need to exclude the root because we can't have
* other log replays overwriting this log as we'll read
* it back in a few more times. This will keep our
* block from being modified, and we'll just bail for
* each subsequent pass.
if (ret == -ENOENT)
ret = btrfs_pin_extent_for_log_replay(fs_info,
if (!ret)
goto next;
btrfs_handle_fs_error(fs_info, ret,
"Couldn't read target root for tree log recovery.");
goto error;
......@@ -6351,7 +6370,6 @@ again:
key.offset = found_key.offset - 1;
wc.replay_dest->log_root = NULL;
......@@ -6359,9 +6377,10 @@ again:
if (ret)
goto error;
if (found_key.offset == 0)
key.offset = found_key.offset - 1;
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment