From db4accf3a3397e2c5973aa99aae52a8f3e864e27 Mon Sep 17 00:00:00 2001
From: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Wed, 15 Aug 2018 13:20:40 +0200
Subject: [PATCH] fsck: don't print corse corruption offset

The exact ciphertext block number (4KiB granularity) is
already printed in the doRead message. Don't cause
confusion by printing the 128KiB-granularity offset as
well.

  doRead 767: corrupt block #4: stupidgcm: message authentication failed
  fsck: error reading file "pa/d7/d14/f10c" (inum 767): 5=input/output error
---
 fsck.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fsck.go b/fsck.go
index e6a695a..fb9258c 100644
--- a/fsck.go
+++ b/fsck.go
@@ -128,7 +128,7 @@ func (ck *fsckObj) file(path string) {
 		result, status := f.Read(buf, off)
 		if !status.Ok() {
 			ck.markCorrupt(path)
-			fmt.Printf("fsck: error reading file %q (inum %d) at offset %d: %v\n", path, inum(f), off, status)
+			fmt.Printf("fsck: error reading file %q (inum %d): %v\n", path, inum(f), status)
 			return
 		}
 		// EOF