diff options
| author | David Sterba <dsterba@suse.com> | 2020-02-05 19:12:16 +0300 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2020-02-12 19:16:57 +0300 |
| commit | e8294f2f6aa6208ed0923aa6d70cea3be178309a (patch) | |
| tree | 795145c91dd1345f0d08430c8b33597467150ff6 /fs/btrfs | |
| parent | ac05ca913e9f3871126d61da275bfe8516ff01ca (diff) | |
| download | linux-e8294f2f6aa6208ed0923aa6d70cea3be178309a.tar.xz | |
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 <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>
Diffstat (limited to 'fs/btrfs')
| -rw-r--r-- | fs/btrfs/disk-io.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c index 7fa9bb79ad08..89422aa8e9d1 100644 --- a/fs/btrfs/disk-io.c +++ b/fs/btrfs/disk-io.c @@ -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; |