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=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 1CC5CC34022 for ; Tue, 18 Feb 2020 02:50:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E84EB206D5 for ; Tue, 18 Feb 2020 02:50:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726237AbgBRCuR (ORCPT ); Mon, 17 Feb 2020 21:50:17 -0500 Received: from tartarus.angband.pl ([54.37.238.230]:33676 "EHLO tartarus.angband.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726185AbgBRCuR (ORCPT ); Mon, 17 Feb 2020 21:50:17 -0500 X-Greylist: delayed 2132 seconds by postgrey-1.27 at vger.kernel.org; Mon, 17 Feb 2020 21:50:16 EST Received: from kilobyte by tartarus.angband.pl with local (Exim 4.92) (envelope-from ) id 1j3sPJ-0006mJ-MM; Tue, 18 Feb 2020 03:14:41 +0100 Date: Tue, 18 Feb 2020 03:14:41 +0100 From: Adam Borowski To: Chris Murphy Cc: Simeon Felis , Btrfs BTRFS , Qu Wenruo Subject: Re: kernel incompatibility? Message-ID: <20200218021441.GA24450@angband.pl> References: <8fb8442b-dbf9-4d4b-42bb-ce460048f891@sfelis.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Junkbait: aaron@angband.pl, zzyx@angband.pl User-Agent: Mutt/1.10.1 (2018-07-13) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kilobyte@angband.pl X-SA-Exim-Scanned: No (on tartarus.angband.pl); SAEximRunCond expanded to false Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Mon, Feb 17, 2020 at 03:55:02PM -0700, Chris Murphy wrote: > On Sun, Feb 16, 2020 at 2:25 AM Simeon Felis wrote: > > I had a btrfs raid1 running on raspbian (linux 4.19 arm) which > > overheated. To fix corruptions I attached the raid1 on my workstation > > (linux 5.5 x86_64) and performed scrub, defrag and --full-balance (not > > necessarily in this order) and fixed the corruptions. > > > > Back on raspbian a mount fails: > > > > root@omv:~# mount /dev/disk/by-label/URAID /mnt/URAID/ > > mount: /mnt/URAID: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error. > > [ 27.304203] BTRFS critical (device sda1): unable to find logical 4306137776128 length 4096 > Because you get this on 4.19.97 (which is the latest kernel on Arch > for ARM v7l), but it mounts OK on 5.5 on x86_64, I'm suspicious it's > an arch specific bug. I don't offhand see any applicable updates > through 4.19.103 that would fix this problem. In particular, you have a filesystem 8TB in size on a 32-bit machine. That's just below the limit of brokenness. If the balance allocated enough new logical addresses... On the other hand, the addresses mentioned here are just below 4TB. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands ⢿⡄⠘⠷⠚⠋⠀ for Privacy. ⠈⠳⣄⠀⠀⠀⠀