Re: [PATCH] btrfs: print message when tree-log replay starts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2/6/20 12:12 AM, David Sterba wrote:
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@xxxxxxxxxxxxxxxxx>
CC: stable@xxxxxxxxxxxxxxx # 4.4+
Signed-off-by: David Sterba <dsterba@xxxxxxxx>
---
  fs/btrfs/disk-io.c | 1 +
  1 file changed, 1 insertion(+)

diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 28622de9e642..295d5ebc9d5e 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -3146,6 +3146,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("start tree-log replay");
  		ret = btrfs_replay_log(fs_info, fs_devices);
  		if (ret) {
  			err = ret;



Reviewed-by: Anand Jain <anand.jain@xxxxxxxxxx>



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux