From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 542E8C4CECF for ; Mon, 23 Sep 2019 18:19:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1807620B7C for ; Mon, 23 Sep 2019 18:19:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="J9FhPVPX" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2440443AbfIWST2 (ORCPT ); Mon, 23 Sep 2019 14:19:28 -0400 Received: from mail-ed1-f51.google.com ([209.85.208.51]:34626 "EHLO mail-ed1-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2440439AbfIWST2 (ORCPT ); Mon, 23 Sep 2019 14:19:28 -0400 Received: by mail-ed1-f51.google.com with SMTP id p10so13851793edq.1 for ; Mon, 23 Sep 2019 11:19:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=7r4F5OxsnmfDikyieFq2a5mGhu6YpOafXGIh6VAAyBs=; b=J9FhPVPXC26QyI9LEq5RuI7yXWlXFa6i88ClBLiaX4yXR8CyjSi0Dq9aZKSgzv+tch +HBUn6yoOmGtEGKETMhaCBb+UccRsyyVG/VeZGPQV/vUqjauWfuXPHiFg29EVrFEFwN6 xg/IlZaHAnHJ0LPUQlhTl1TTUJ+N4+bQ9NLDRza5nze68RP/W5jaNOwkyPLFvJFBQOVy dVfP8fzzSZSCK8/lXEDkjI0rganMJWTRXWKqcOa1szXY3d9xUTg/C7ELe3G3oPpX7kY4 TTN2FYyt01z/+d0QwTnaw7x+LFh6V2o/S0UrnKe4bbuh28KhfOTRhxbhnJoZMIWtL1NO Brgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=7r4F5OxsnmfDikyieFq2a5mGhu6YpOafXGIh6VAAyBs=; b=fZQD+VzSynB/Jl4iO330U//UKv38djVRMPaDJzkTgImGGRGrm6zDU2GSNtMjXATKWR h0t74gMWBPZ0omSD5B3BAsUFsB2uO6axZ/6Vu2ga3XuuJE35uUwSbBw/kpoo9MgqT78J hfVwTTjK3LgVcqiZQVchcmlSLh8Meb2W0pgfU3EnfKrFBaUTbFhsZzcawuviVGAFoC/I i4urmb8g4dX+W1Q3NjdS/xZnIv1dgcaWfStS/pCMn8pi+sispNKnDSQLiOJbZg0VEYXP iQJ6gTpQ1HwDdtsZvcsA8kCxcxrZkB1XiKfpgx58A6rb89u6AhNncv0xQ3T3MD0Jsq8I bKWA== X-Gm-Message-State: APjAAAUdGsg4NOqEsu0GxVsXhVK5hJUaeifU2lmR7p/nLrFdn0Ew8M9v O3ddoQWE3a7VIDvVNc5PcMom6UO+rD8= X-Google-Smtp-Source: APXvYqwdujIjhVYyonhC+XvEEJ1yG4Ooa/BOg0nv2MU/qyAfGpTD9W7HiviEk9TVH0vEhceedleOew== X-Received: by 2002:a50:a7c4:: with SMTP id i62mr1516937edc.92.1569262766250; Mon, 23 Sep 2019 11:19:26 -0700 (PDT) Received: from MHPlaptop (xd520f268.cust.hiper.dk. [213.32.242.104]) by smtp.gmail.com with ESMTPSA id v4sm2525528edy.54.2019.09.23.11.19.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Sep 2019 11:19:25 -0700 (PDT) From: To: Subject: BTRFS checksum mismatch - false positives Date: Mon, 23 Sep 2019 20:19:24 +0200 Message-ID: <000f01d5723b$6e3d0f70$4ab72e50$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdVyO22XlGIcXaePSIiSisyS1vf28A== Content-Language: en-us Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org Dear BTRFS mailing list, I'm running BTRFS on my Synology Diskstation and they have referred me to the BTRFS developers. For a while I have had quite a few (tens - not hundreds) checksum mismatch errors on my device (around 6 TB data). It runs BTRFS on SHR (Synology Hybrid Raid). Most of these checksum mismatches, though, do not seem "real". Most of the files are identical to the original files (checked by binary comparison and by recalculated MD5 hashes). What can explain that problem? I thought BTRFS only reported checksum mismatch errors, when it cannot self-heal the files? Best Hoegge