diff options
-rw-r--r-- | fs/btrfs/super.c | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index a1a6c296ddcd..ef2415896b06 100644 --- a/fs/btrfs/super.c +++ b/fs/btrfs/super.c | |||
@@ -116,7 +116,16 @@ static void btrfs_handle_error(struct btrfs_fs_info *fs_info) | |||
116 | if (fs_info->fs_state & BTRFS_SUPER_FLAG_ERROR) { | 116 | if (fs_info->fs_state & BTRFS_SUPER_FLAG_ERROR) { |
117 | sb->s_flags |= MS_RDONLY; | 117 | sb->s_flags |= MS_RDONLY; |
118 | printk(KERN_INFO "btrfs is forced readonly\n"); | 118 | printk(KERN_INFO "btrfs is forced readonly\n"); |
119 | btrfs_scrub_cancel(fs_info); | 119 | /* |
120 | * Note that a running device replace operation is not | ||
121 | * canceled here although there is no way to update | ||
122 | * the progress. It would add the risk of a deadlock, | ||
123 | * therefore the canceling is ommited. The only penalty | ||
124 | * is that some I/O remains active until the procedure | ||
125 | * completes. The next time when the filesystem is | ||
126 | * mounted writeable again, the device replace | ||
127 | * operation continues. | ||
128 | */ | ||
120 | // WARN_ON(1); | 129 | // WARN_ON(1); |
121 | } | 130 | } |
122 | } | 131 | } |