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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D7233C433EF for ; Mon, 22 Nov 2021 10:36:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235207AbhKVKju (ORCPT ); Mon, 22 Nov 2021 05:39:50 -0500 Received: from smtp-out1.suse.de ([195.135.220.28]:43598 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235098AbhKVKjt (ORCPT ); Mon, 22 Nov 2021 05:39:49 -0500 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id F2C0E218E1; Mon, 22 Nov 2021 10:36:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1637577401; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=flewUspR43JjmTfaByVLpcP/+rZMRLElSGYI+VuID1Y=; b=bOZDKd61EBXIio5kV+W7V7zfBGq8zq+dJfZCaQsjEe3sQzww38Z2pbYm3i4Uiv6ymekNyW 66JaERvOJxpuHsy5alUhYw+gajb4T+j6vXDmLTBTpa0GfP3iSN2haJv0bZDRZVU75O9ICr W2VAfNl9C2renWT69u+Qr2YVp8XywtA= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id C86F913B9E; Mon, 22 Nov 2021 10:36:41 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id OlAKLrlym2F7egAAMHmgww (envelope-from ); Mon, 22 Nov 2021 10:36:41 +0000 Subject: Re: read time tree block corruption detected To: x8062 Cc: linux-btrfs@vger.kernel.org References: <56d93523.27d4.17d461bc3c6.Coremail.ericleaf@126.com> <7f681c79.4eba.17d471d802e.Coremail.ericleaf@126.com> From: Nikolay Borisov Message-ID: Date: Mon, 22 Nov 2021 12:36:41 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <7f681c79.4eba.17d471d802e.Coremail.ericleaf@126.com> Content-Type: text/plain; charset=gbk Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On 22.11.21 §Ô. 12:07, x8062 wrote: > At 2021-11-22 15:24:38, "Nikolay Borisov" wrote: >> >> >> On 22.11.21 §Ô. 7:26, x8062 wrote: >>> Hello, >>> I got periodic warns in my linux console. in dmesg it is the following pasted text. >>> At https://btrfs.wiki.kernel.org/index.php/Tree-checker I learned it may be a error, so i send the message. Hopefully it could help, Thanks in advance! >>> >>> [ 513.900852] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465 >>> >> >> >> You have faulty ram, since 393 has the 17th bit set to 0 whilst has it >> set to 1. So your ram is clearly corrupting bits. I advise you run a >> memtest tool and look for possibly changing the faulty ram module. > > Thank you, can't believe the ram is not so stable. I'll run a memtest later. Actually according to the output this is a read-time corruption. THis means the corrupted data has already been written to disk, likely by an older kernel that didn't have the tree cherk code. So running a memcheck is still useful to prevent future corruption. As far as the corrupted files goes - well its data is corrupted. It can technically be fixed, but you'd have to do it yourself. Or alternatively go back on an older kernel i.e pre- 5.11 and try to copy that particular file (inode 2394634). >