[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20220923132548.1701519-1-lkundrak@v3.sk>
Date: Fri, 23 Sep 2022 15:25:48 +0200
From: Lubomir Rintel <lkundrak@...sk>
To: Theodore Ts'o <tytso@....edu>
Cc: linux-ext4@...r.kernel.org, Lubomir Rintel <lkundrak@...sk>
Subject: [PATCH] tune2fs: fix an error message
$ tune2fs -O ^has_journal -ff /dev/sdh2
Recovering journal. tune2fs: Unknown code ____ 251 while recovering journal.
Before: Please run e2fsck -fy -O.
After: Please run e2fsck -fy /dev/sdh2.
Note this doesn't fix the "Unknown code" message, just the "Please run
e2fsck" one.
Signed-off-by: Lubomir Rintel <lkundrak@...sk>
---
misc/tune2fs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/misc/tune2fs.c b/misc/tune2fs.c
index 088f87e5..c85737ad 100644
--- a/misc/tune2fs.c
+++ b/misc/tune2fs.c
@@ -3343,7 +3343,7 @@ _("Warning: The journal is dirty. You may wish to replay the journal like:\n\n"
if (retval) {
com_err("tune2fs", retval,
"while recovering journal.\n");
- printf(_("Please run e2fsck -fy %s.\n"), argv[1]);
+ printf(_("Please run e2fsck -fy %s.\n"), device_name);
rc = 1;
goto closefs;
}
--
2.37.3
Powered by blists - more mailing lists