Commit 2a902b48 authored Feb 05, 2020 by David Sterba Committed by Greg Kroah-Hartman Feb 19, 2020

btrfs: print message when tree-log replay starts



commit e8294f2f6aa6208ed0923aa6d70cea3be178309a upstream.

There's no logged information about tree-log replay although this is
something that points to previous unclean unmount. Other filesystems
report that as well.

Suggested-by: Chris Murphy <lists@colorremedies.com>
CC: stable@vger.kernel.org # 4.4+
Reviewed-by: Anand Jain <anand.jain@oracle.com>
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

parent 67d9c9e4

fs/btrfs/disk-io.c

+1 −0

Original line number	Diff line number	Diff line
		@@ -3117,6 +3117,7 @@ int open_ctree(struct super_block *sb,
		/* do not make disk changes in broken FS or nologreplay is given */
		if (btrfs_super_log_root(disk_super) != 0 &&
		!btrfs_test_opt(fs_info, NOLOGREPLAY)) {
		btrfs_info(fs_info, "start tree-log replay");
		ret = btrfs_replay_log(fs_info, fs_devices);
		if (ret) {
		err = ret;