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.8 required=3.0 tests=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 4B9EAC43331 for ; Fri, 8 Nov 2019 00:08:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E40B82085B for ; Fri, 8 Nov 2019 00:08:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726320AbfKHAIl (ORCPT ); Thu, 7 Nov 2019 19:08:41 -0500 Received: from devico.uberspace.de ([185.26.156.185]:46128 "EHLO devico.uberspace.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725906AbfKHAIk (ORCPT ); Thu, 7 Nov 2019 19:08:40 -0500 Received: (qmail 26317 invoked from network); 8 Nov 2019 00:08:37 -0000 Received: from unknown (HELO localhost) (2003:f9:f716:5d00:127b:44ff:fe50:1c77) by devico.uberspace.de with SMTP; 8 Nov 2019 00:08:37 -0000 From: Leonard Lausen To: Qu Wenruo , linux-btrfs@vger.kernel.org Subject: Re: __btrfs_free_extent error after suspend resume In-Reply-To: <7d16efdd-f6f9-9580-d361-a00251b6634c@gmx.com> References: <878sotrhyi.fsf@lausen.nl> <87blto1lwx.fsf@lausen.nl> <7d16efdd-f6f9-9580-d361-a00251b6634c@gmx.com> Date: Fri, 08 Nov 2019 00:08:33 +0000 Message-ID: <87o8xnw7pa.fsf@lausen.nl> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org Qu Wenruo writes: >> btrfs check --readonly /dev/$NAME >> >> runs out of 16GB of memory within 20 seconds and is killed by the >> kernel. > > That's why we have btrfs check --mode=lowmem Thank you for pointing this out Qu. btrfs check --mode=lowmem finds checksum verify failed on 1383731085312 found 000000CC wanted FFFFFFF5 checksum verify failed on 1383731085312 found 000000CC wanted FFFFFFF5 bad tree block 1383731085312, bytenr mismatch, want=1383731085312, have=15281531241332003907 ERROR: shared extent 1776065458176 referencer lost (parent: 1383731085312) ERROR: errors found in extent allocation tree or chunk allocation When creating a backup of the home directory after the filesystem was mounted ro, only a single log file could not be included in the backup due to failure to read it. Is there any way to fix the filesystem, given that btrfs check --mode=lowmem does not support --repair? Do you think this corruption is related to some kernel bug, triggered during suspend / resume cycle? Or could it be simply a harddrive (SSD) failure? (An extended disk self test did not report any errors though.) Best regards Leonard