btrfs-progs: lowmem check: Reword an unclear error message about file extent gap
diff mbox

Message ID 20171110094710.21193-1-lufq.fnst@cn.fujitsu.com
State New
Headers show

Commit Message

Lu Fengqi Nov. 10, 2017, 9:47 a.m. UTC
This error occurs when no_holes is not set, but there is a gap
before the file extent.

Signed-off-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
---

Really ashamed, I made the mistake about the meaning of this word.

 cmds-check.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

Comments

David Sterba Nov. 27, 2017, 6:55 p.m. UTC | #1
On Fri, Nov 10, 2017 at 05:47:10PM +0800, Lu Fengqi wrote:
> This error occurs when no_holes is not set, but there is a gap
> before the file extent.
> 
> Signed-off-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>

Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Patch
diff mbox

diff --git a/cmds-check.c b/cmds-check.c
index a93ac2c8..5eab0143 100644
--- a/cmds-check.c
+++ b/cmds-check.c
@@ -5868,8 +5868,9 @@  static int check_file_extent(struct btrfs_root *root, struct btrfs_key *fkey,
 		if (!repair || ret) {
 			err |= FILE_EXTENT_ERROR;
 			error(
-		"root %llu EXTENT_DATA[%llu %llu] interrupt, should start at %llu",
-			root->objectid, fkey->objectid, fkey->offset, *end);
+"root %llu EXTENT_DATA[%llu %llu] gap exists, expected: EXTENT_DATA[%llu %llu]",
+			root->objectid, fkey->objectid, fkey->offset,
+			fkey->objectid, *end);
 		}
 	}