diff options
| author | David Sterba <dsterba@suse.com> | 2020-02-05 17:12:28 +0100 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2020-02-12 17:17:00 +0100 |
| commit | 10a3a3edc5b89a8cd095bc63495fb1e0f42047d9 (patch) | |
| tree | fd2da93f686786d6572c94125a43f58be12494ce | |
| parent | btrfs: print message when tree-log replay starts (diff) | |
| download | linux-10a3a3edc5b89a8cd095bc63495fb1e0f42047d9.tar.xz linux-10a3a3edc5b89a8cd095bc63495fb1e0f42047d9.zip | |
btrfs: log message when rw remount is attempted with unclean tree-log
A remount to a read-write filesystem is not safe when there's tree-log
to be replayed. Files that could be opened until now might be affected
by the changes in the tree-log.
A regular mount is needed to replay the log so the filesystem presents
the consistent view with the pending changes included.
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>
| -rw-r--r-- | fs/btrfs/super.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index 0616a5434793..67c63858812a 100644 --- a/fs/btrfs/super.c +++ b/fs/btrfs/super.c @@ -1834,6 +1834,8 @@ static int btrfs_remount(struct super_block *sb, int *flags, char *data) } if (btrfs_super_log_root(fs_info->super_copy) != 0) { + btrfs_warn(fs_info, + "mount required to replay tree-log, cannot remount read-write"); ret = -EINVAL; goto restore; } |