summaryrefslogtreecommitdiffstats
path: root/fs/ext4
diff options
context:
space:
mode:
authorSimon Ruderich <simon@ruderich.org>2017-10-18 19:06:37 +0200
committerTheodore Ts'o <tytso@mit.edu>2017-10-18 19:06:37 +0200
commitd98bf8cd11985256b96d610453baf1ff8814ff87 (patch)
tree5ad9d7583fb09d427ec462f56a32dabebbe86aab /fs/ext4
parentDocumentation: fix little inconsistencies (diff)
downloadlinux-d98bf8cd11985256b96d610453baf1ff8814ff87.tar.xz
linux-d98bf8cd11985256b96d610453baf1ff8814ff87.zip
ext4: mention noload when recovering on read-only device
Help the user to find the appropriate mount option to continue mounting the file system on a read-only device if the journal requires recovery. Signed-off-by: Simon Ruderich <simon@ruderich.org> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/ext4')
-rw-r--r--fs/ext4/super.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 64d5e9e78dbc..3a278faf5868 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -4616,7 +4616,8 @@ static int ext4_load_journal(struct super_block *sb,
"required on readonly filesystem");
if (really_read_only) {
ext4_msg(sb, KERN_ERR, "write access "
- "unavailable, cannot proceed");
+ "unavailable, cannot proceed "
+ "(try mounting with noload)");
return -EROFS;
}
ext4_msg(sb, KERN_INFO, "write access will "