From patchwork Thu Sep 14 10:23:06 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Simon Ruderich X-Patchwork-Id: 813759 Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=linux-ext4-owner@vger.kernel.org; receiver=) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3xtF3j56LJz9s0Z for ; Thu, 14 Sep 2017 20:23:13 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751586AbdINKXI (ORCPT ); Thu, 14 Sep 2017 06:23:08 -0400 Received: from zucker2.schokokeks.org ([178.63.68.90]:40949 "EHLO zucker2.schokokeks.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751526AbdINKXI (ORCPT ); Thu, 14 Sep 2017 06:23:08 -0400 Received: from localhost ([::1]) (AUTH: PLAIN simon@ruderich.org, TLS: TLSv1/SSLv3, 256bits, ECDHE-RSA-AES256-GCM-SHA384) by zucker.schokokeks.org with ESMTPSA; Thu, 14 Sep 2017 12:23:07 +0200 id 00000000000000E0.0000000059BA588B.00004E3C Date: Thu, 14 Sep 2017 12:23:06 +0200 From: Simon Ruderich To: linux-ext4@vger.kernel.org Subject: [PATCH] ext4: mention noload when recovering on read-only device Message-ID: <977f189abb1ff382dedd6916b7140081d47d3e8d.1505383806.git.simon@ruderich.org> Mime-Version: 1.0 Content-Disposition: inline User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org 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 --- 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 "