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.6 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, URIBL_BLOCKED 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 0DBF9C38A24 for ; Thu, 7 May 2020 05:43:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CF290207DD for ; Thu, 7 May 2020 05:43:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="cUmokudZ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725841AbgEGFnp (ORCPT ); Thu, 7 May 2020 01:43:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51756 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725783AbgEGFno (ORCPT ); Thu, 7 May 2020 01:43:44 -0400 Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 64A9CC061A0F for ; Wed, 6 May 2020 22:43:44 -0700 (PDT) Received: by mail-lj1-x232.google.com with SMTP id h4so4906837ljg.12 for ; Wed, 06 May 2020 22:43:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=BaQbZ6HqRNDwFrTSK9fjjOiYn2q9Tn59O5Q+HcnYh6E=; b=cUmokudZI4RlBjtV3WeM4yFCqHXkoz4iEdyBYz46d6geymAy5TiZRXEmEInLGATOZ3 NetS6PJOw1pF8A9JapZVsvo+NaIL6E+oeZ1P9CewBu2j4EYP4NipUHeRTiFo1zYGtEvG jZrWP93K5a+cHSMZ9AxoC+Zt1hmXisLwPhzi0bi26jlSx8djYs8P+EvfgAEF7ccavJl6 C+PjiRUzwCPS/AFoaKMMr06lbLovXxInF9vmzyDnUrlhWXu1d6iviIk1jbE0jNhkTkss ncPyEfsCToMsigQveL/5/RJpAnK4dL8Es3PNyxjq5IvAoF9RUGqtmX9lUat3PSqA6SBG czbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=BaQbZ6HqRNDwFrTSK9fjjOiYn2q9Tn59O5Q+HcnYh6E=; b=qkc0EXjkjjZpA4C+cqtrB2WYfdtTFdj8+YNGHCq3XEma6j/0yt3UlVaAxoo4ll24SY /o38j0IIx+ldNqnKAA7CFFwaH5fiDDBd5J/QPnv02oz150RHHWshBTbs/tR9QCKoJY+U f8iC0l6ppf9n+LTG97wOxccliCJebKfcLDXURyfL0zKXnrIBRub3eUH2U5Sh2U+Zx7BP PGGaaFR7E6oDqHNs1KdkV2L9LhrsdJejyVhKIGCeBAzM/RzWaeP2WTDLPU0E9ZjqVtJ1 Fc2AX4DiLZKJmIM51Go5nQ6u+6qcrRJU//8/Y7Pvstb+rGviexjoQtldo3YiRWLmiNlF 7J0g== X-Gm-Message-State: AGi0PuYrHuM8ICBavOzET+ojlCt3AlrMQR1T2cQRqTQ61uE2npHAP42q fbuw2t6tUsu7BcBJ1LHvLP/Tk9jKLDHT1tp5XCLaBKzcLkg= X-Google-Smtp-Source: APiQypI8leUL2wa+1+Th/kkbzRCoTY15sjhgl6zgmecYEFxO55u/otlZDlvHNUSWbZwG4lkqcfWqn5nZJq6EwIncvFg= X-Received: by 2002:a2e:7610:: with SMTP id r16mr7540423ljc.156.1588830222508; Wed, 06 May 2020 22:43:42 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tyler Richmond Date: Thu, 7 May 2020 01:43:32 -0400 Message-ID: Subject: Re: Fwd: Read time tree block corruption detected To: Qu Wenruo , Chris Murphy Cc: Btrfs BTRFS Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org Well, the repair doesn't look terribly successful. parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 parent transid verify failed on 218620880703488 wanted 6875841 found 687622= 4 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=3D225049956061184 item=3D84 parent level=3D1 child level=3D4 ERROR: failed to zero log tree: -17 ERROR: attempt to start transaction over already running one WARNING: reserved space leaked, flag=3D0x4 bytes_reserved=3D4096 extent buffer leak: start 225049066086400 len 4096 extent buffer leak: start 225049066086400 len 4096 WARNING: dirty eb leak (aborted trans): start 225049066086400 len 4096 extent buffer leak: start 225049066094592 len 4096 extent buffer leak: start 225049066094592 len 4096 WARNING: dirty eb leak (aborted trans): start 225049066094592 len 4096 extent buffer leak: start 225049066102784 len 4096 extent buffer leak: start 225049066102784 len 4096 WARNING: dirty eb leak (aborted trans): start 225049066102784 len 4096 extent buffer leak: start 225049066131456 len 4096 extent buffer leak: start 225049066131456 len 4096 WARNING: dirty eb leak (aborted trans): start 225049066131456 len 4096 What is going on? On Wed, May 6, 2020 at 9:30 PM Tyler Richmond wrot= e: > > Chris, I had used the correct mountpoint in the command. I just edited > it in the email to be /mountpoint for consistency. > > Qu, I'll try the repair. Fingers crossed! > > On Wed, May 6, 2020 at 9:13 PM Qu Wenruo wrote: > > > > > > > > On 2020/5/7 =E4=B8=8A=E5=8D=885:54, Tyler Richmond wrote: > > > Hello, > > > > > > I looked up this error and it basically says ask a developer to > > > determine if it's a false error or not. I just started getting some > > > slow response times, and looked at the dmesg log to find a ton of > > > these errors. > > > > > > [192088.446299] BTRFS critical (device sdh): corrupt leaf: root=3D5 > > > block=3D203510940835840 slot=3D4 ino=3D1311670, invalid inode generat= ion: > > > has 18446744073709551492 expect [0, 6875827] > > > [192088.449823] BTRFS error (device sdh): block=3D203510940835840 rea= d > > > time tree block corruption detected > > > [192088.459238] BTRFS critical (device sdh): corrupt leaf: root=3D5 > > > block=3D203510940835840 slot=3D4 ino=3D1311670, invalid inode generat= ion: > > > has 18446744073709551492 expect [0, 6875827] > > > [192088.462773] BTRFS error (device sdh): block=3D203510940835840 rea= d > > > time tree block corruption detected > > > [192088.464711] BTRFS critical (device sdh): corrupt leaf: root=3D5 > > > block=3D203510940835840 slot=3D4 ino=3D1311670, invalid inode generat= ion: > > > has 18446744073709551492 expect [0, 6875827] > > > [192088.468457] BTRFS error (device sdh): block=3D203510940835840 rea= d > > > time tree block corruption detected > > > > > > btrfs device stats, however, doesn't show any errors. > > > > > > Is there anything I should do about this, or should I just continue > > > using my array as normal? > > > > This is caused by older kernel underflow inode generation. > > > > Latest btrfs-progs can fix it, using btrfs check --repair. > > > > Or you can go safer, by manually locating the inode using its inode > > number (1311670), and copy it to some new location using previous > > working kernel, then delete the old file, copy the new one back to fix = it. > > > > Thanks, > > Qu > > > > > > > > Thank you! > > > > >