FAILED: patch "[PATCH] btrfs: print message when tree-log replay starts" failed to apply to 4.4-stable tree
Subsystems (2)
[email protected]
maintainerThe patch below does not apply to the 4.4-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From e8294f2f6aa6208ed0923aa6d70cea3be178309a Mon Sep 17 00:00:00 2001
From: David Sterba <[email protected]>
Date: Wed, 5 Feb 2020 17:12:16 +0100
Subject: [PATCH] btrfs: print message when tree-log replay starts
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 <[email protected]>
CC [email protected] # 4.4+
Reviewed-by Anand Jain <[email protected]>
Reviewed-by Johannes Thumshirn <[email protected]>
Signed-off-by David Sterba <[email protected]>
fs/btrfs/disk-io.c +1 -0
@@ -3164,6 +3164,7 @@ int __cold 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;