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 39742C636CC for ; Wed, 15 Feb 2023 20:17:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229454AbjBOURE (ORCPT ); Wed, 15 Feb 2023 15:17:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40902 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229505AbjBOURD (ORCPT ); Wed, 15 Feb 2023 15:17:03 -0500 Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89ADF2A6FB for ; Wed, 15 Feb 2023 12:17:01 -0800 (PST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 079313200900 for ; Wed, 15 Feb 2023 15:17:00 -0500 (EST) Received: from imap50 ([10.202.2.100]) by compute5.internal (MEProxy); Wed, 15 Feb 2023 15:17:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= colorremedies.com; h=cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1676492220; x= 1676578620; bh=oEGdyz/W/1KbVi5d8As5uAOPTBYLeUpadP7LQriPkLQ=; b=T 5MknTdSfVSmRPv4LLPc/mteC0cPsQEmAgBRq0KB95pVabfKBpbUTaMhviXR8Qu// PteImq63LdKxCZ/of9vr4zLEZRBBOxF+5H6BKzkuNfNKQrWbmdIe77nCP9LC5VvB qftnwQnswdiYmu+d+f3cUCbZypf9TbxHBgF9YCwo8G+pyjkU0yhMItt+Cwq6++3E Ic9/0fcaGP+nNsPF6Oleb8FV7hB6OgMo4WjL4/eQJ6xiDwEkJNK2SjVl9frJzRkM InGnoaRK3cDDJIHkcETUqTo+nsNWLT+YISASynSCuP7CMvJ8+CeB5Fsk9NQrgiBj pwvumuqew7R+raKptB9jA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1676492220; x=1676578620; bh=oEGdyz/W/1KbVi5d8As5uAOPTBYL eUpadP7LQriPkLQ=; b=hKrE4k0lSagsYQWmq1TFJaLH76GSst7Ru0Lf9XbWic4c MEFyCM3P9FZNqufyWerIiVVTO12YCLTUj73ntD1YszYgn3qhK8X5ega5L2fNJlIi AeG1dt7PGoxxDp2x6oaSTbpz580GkpunqPoIh5LT8mwywVBu+G/1TAerNZpQapi3 x7IAbU+pgmaqgHQJS1tNsxAf4Z7tBxfkAR+L59jtq5c82eDc7FpsgyYgDhUN0OYy VEHnSZaBeJdj/1xpEq/U0PLM4UbiPDLQ21gW8d5Ca5mAsuJCUgSYeXuyzjGopWfK dRLzJ3SoSb5oinFs3XR8gh04zQ3MMWMAjt2Y802Otw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeihedguddvjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfvehh rhhishcuofhurhhphhihfdcuoegthhhrihhssegtohhlohhrrhgvmhgvughivghsrdgtoh hmqeenucggtffrrghtthgvrhhnpedtvdfggfeikeffkedvheefveffhedujeeugedtudfg ieefgfffiedufffhgefgkeenucffohhmrghinheprhgvughhrghtrdgtohhmnecuvehluh hsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheptghhrhhishestgho lhhorhhrvghmvgguihgvshdrtghomh X-ME-Proxy: Feedback-ID: i07814636:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 56DA01700127; Wed, 15 Feb 2023 15:17:00 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-156-g081acc5ed5-fm-20230206.001-g081acc5e Mime-Version: 1.0 Message-Id: <124a916c-786b-42ec-bc9d-db97bb081881@app.fastmail.com> In-Reply-To: References: Date: Wed, 15 Feb 2023 15:16:39 -0500 From: "Chris Murphy" To: "Btrfs BTRFS" Subject: Re: LMDB mdb_copy produces a corrupt database on btrfs, but not on ext4 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Wed, Feb 15, 2023, at 3:04 PM, Chris Murphy wrote: > Downstream bug report, reproducer test file, and gdb session transcript > https://bugzilla.redhat.com/show_bug.cgi?id=2169947 > > I speculated that maybe it's similar to the issue we have with VM's > when O_DIRECT is used, but it seems that's not the case here. I can reproduce the mismatching checksums whether the test files are datacow or nodatacow (using chattr +C). There are no kernel messages during the tests. kernel 6.2rc7 in my case; and in the bug report kernel series 6.1, 6.0, and 5.17 reproduce the problem. -- Chris Murphy