From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot0-f176.google.com ([74.125.82.176]:50016 "EHLO mail-ot0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753107AbdKFUEt (ORCPT ); Mon, 6 Nov 2017 15:04:49 -0500 Received: by mail-ot0-f176.google.com with SMTP id c47so10094680otj.6 for ; Mon, 06 Nov 2017 12:04:49 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1484297967.48018.1508985286675@email.1and1.com> From: Chris Murphy Date: Mon, 6 Nov 2017 13:04:48 -0700 Message-ID: Subject: Re: btrfs send yields "ERROR: send ioctl failed with -5: Input/output error" To: Chris Murphy , Qu Wenruo Cc: Zak Kohler , "Lakshmipathi.G" , btrfs Content-Type: text/plain; charset="UTF-8" Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Sun, Oct 29, 2017 at 1:05 PM, Chris Murphy wrote: > On Thu, Oct 26, 2017 at 4:34 AM, Zak Kohler wrote: > >> I will gladly repeat this process, but I am very concerned why this >> corruption happened in the first place. > > Right. So everyone who can, needs to run the three scrubs on all > available Btrfs volumes/devices and see if they get any discrepancies. I've just done this test with five Btrfs volumes of various ages, and a total of a few TB. There were no errors, and no discrepancies between the three scrubs. What is needed for more thorough testing is corrupt metadata and data (unrelated), and see how the three scrubs report those corruptions. More information in the new thread "feedback on three different scrub methods" -- Chris Murphy