aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMasatake YAMATO <yamato@redhat.com>2017-09-15 13:42:18 -0500
committerEric Sandeen <sandeen@redhat.com>2017-09-15 13:42:18 -0500
commit67ea25fe9d663f69b550b39ce86b074534ae7c85 (patch)
tree2fd3a1e1db8cbd946f0444f5463aca7d28da9450
parent99a13e2dac70d219a7039da04fb07cc48fd3fca0 (diff)
downloadxfsprogs-dev-67ea25fe9d663f69b550b39ce86b074534ae7c85.tar.gz
xfs_repair: don't use do_warn for normal log message
In some case, exit status of xfs_repair -n is different even for the same file system when -v is specified or not. This patch fixes this behavior. If -v is specified, do_warn() is used in zero_log() for printing a normal message. That makes the exit status to 1 though there is no dirtiness in the file system. Signed-off-by: Masatake YAMATO <yamato@redhat.com> Reviewed-by: Eric Sandeen <sandeen@redhat.com> [sandeen: edit changelog for brevity] Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
-rw-r--r--repair/phase2.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/repair/phase2.c b/repair/phase2.c
index 0085732b39..992e997b03 100644
--- a/repair/phase2.c
+++ b/repair/phase2.c
@@ -86,7 +86,7 @@ zero_log(
exit(2);
} else {
if (verbose) {
- do_warn(
+ do_log(
_("zero_log: head block %" PRId64 " tail block %" PRId64 "\n"),
head_blk, tail_blk);
}