linux-ext4 - [PATCH] ext4: mention noload when recovering on read-only device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 14 Sep 2017 12:23:06 +0200
From:   Simon Ruderich <simon@...erich.org>
To:     linux-ext4@...r.kernel.org
Subject: [PATCH] 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@...erich.org>
---
Hello,

I tried to mount an ext4 which required recovery from a read-only
device and stumbled over this error. I freaked out for a second
(trying to restore from a backup) and it took me a (short) while
to figure out what to do and I thought it would be useful to give
the user a hand by pointing to the required mount option.

Regards
Simon

 fs/ext4/super.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index d61a70e2193a..f497b79da5cc 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -4589,7 +4589,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 "
-- 
2.14.1

-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9