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=-1.0 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 1F2D4C4CEC6 for ; Thu, 12 Sep 2019 14:39:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0063D208E4 for ; Thu, 12 Sep 2019 14:39:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732715AbfILOj4 (ORCPT ); Thu, 12 Sep 2019 10:39:56 -0400 Received: from mailgw-01.dd24.net ([193.46.215.41]:48554 "EHLO mailgw-01.dd24.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732250AbfILOj4 (ORCPT ); Thu, 12 Sep 2019 10:39:56 -0400 Received: from mailpolicy-01.live.igb.homer.key-systems.net (mailpolicy-02.live.igb.homer.key-systems.net [192.168.1.27]) by mailgw-01.dd24.net (Postfix) with ESMTP id 1A40D5FDD6; Thu, 12 Sep 2019 14:39:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mailpolicy-02.live.igb.homer.key-systems.net Received: from smtp.dd24.net ([192.168.1.35]) by mailpolicy-01.live.igb.homer.key-systems.net (mailpolicy-02.live.igb.homer.key-systems.net [192.168.1.25]) (amavisd-new, port 10235) with ESMTP id B2uCtoWRV3Jl; Thu, 12 Sep 2019 14:39:53 +0000 (UTC) Received: from gar-nb-etp23.garching.physik.uni-muenchen.de (unknown [141.84.41.131]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.dd24.net (Postfix) with ESMTPSA; Thu, 12 Sep 2019 14:39:53 +0000 (UTC) Message-ID: <41d5dae3587efa5c19262a230e3c459f8e14159b.camel@scientia.net> Subject: Re: Massive filesystem corruption since kernel 5.2 (ARCH) From: Christoph Anton Mitterer To: fdmanana@gmail.com Cc: linux-btrfs Date: Thu, 12 Sep 2019 16:39:52 +0200 In-Reply-To: References: <11e4e889f903ddad682297c4420faeb0245414cf.camel@scientia.net> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Thu, 2019-09-12 at 15:28 +0100, Filipe Manana wrote: > This is case 2), the corruption with the error messages > "parent transid verify failed ..." in dmesg/syslog after mounting the > filesystem again. Hmm so "at least" it will never go unnoticed, right? This is IMO a pretty important advise, as people may want to compare their current data with that of backups... if silent corruption would have been possible. Cheers, Chris.