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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 E9EA9C433F5 for ; Tue, 7 Sep 2021 23:21:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C8FCE60249 for ; Tue, 7 Sep 2021 23:21:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243963AbhIGXWN (ORCPT ); Tue, 7 Sep 2021 19:22:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52624 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234094AbhIGXWM (ORCPT ); Tue, 7 Sep 2021 19:22:12 -0400 Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 01B54C061575 for ; Tue, 7 Sep 2021 16:21:06 -0700 (PDT) Received: by mail-io1-xd2a.google.com with SMTP id a22so685995iok.12 for ; Tue, 07 Sep 2021 16:21:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wyrick.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=8FeEn7CJ6fjEba7wD7kxkjSHDsiRZYkp2qfVBue1vqg=; b=Lfw/BQTxBTXNapby8mSCIQZI8yM1v/+Jth1QmEDwf5LiLtKrvaOtMsmVIEdv90Spgv VYhB9l8YnF3lHDc/2NXMSpMj+jMXbLlYxaNQIff1bhbK324CLAZWOo94Ef6N4bf/b5C8 cNz7PbYoFAeX+9t8vIfIGapv0RAhDflPkfn90= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=8FeEn7CJ6fjEba7wD7kxkjSHDsiRZYkp2qfVBue1vqg=; b=gv0JUDwteIhZY+zVQxnk0ICkO0Ct5wRwSDSojZuDTjc7Q7GX9Wcv7kB2kDnrZcSajv xZ9kSv0kPRaoHi7lJMkzO4J7o8dXUAQd7j+5UYrFGlc7qMdbwW/iE4CRMvQ9YC/nzJCA +67FmzYRr0EfxMsxQ7IrtwaOkMwPOqst2t0gl3dGePA2qFOqzd05LBd7mlbmsxWJ830x yAwgJ0mLJ5PsMRKjdzpnQl1sIOByP8ELuXADM14P8ooVyqul+v4gvfgQgQbh7YXwL6hE Dh4/KcqqqhZvTcV2gXqyly0Okl6KWBDcIpMkrZKju0NEibrOWbnnQ6TdX909bQ0c2HBT GdMg== X-Gm-Message-State: AOAM533IrTj/FZQ03BDBJfY4O7908Sa/KCG2c49nOqUVo5uxb6NSXfnL e9ZYWB/sXAZTZAfcyofN8TOmEiJ4eyuQ2g== X-Google-Smtp-Source: ABdhPJwXAVUjoGHeCHebDduKdtkE1q/2UVks5ratB5LiSz8BuoWE3kXJo5s6T8EbjzKH3JGhFWTkNQ== X-Received: by 2002:a5e:dd42:: with SMTP id u2mr550844iop.157.1631056865080; Tue, 07 Sep 2021 16:21:05 -0700 (PDT) Received: from mail-il1-f179.google.com (mail-il1-f179.google.com. [209.85.166.179]) by smtp.gmail.com with ESMTPSA id k21sm181822ioh.38.2021.09.07.16.21.04 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Sep 2021 16:21:04 -0700 (PDT) Received: by mail-il1-f179.google.com with SMTP id j15so379594ila.1 for ; Tue, 07 Sep 2021 16:21:04 -0700 (PDT) X-Received: by 2002:a92:b301:: with SMTP id p1mr520438ilh.10.1631056864356; Tue, 07 Sep 2021 16:21:04 -0700 (PDT) MIME-Version: 1.0 References: <3139b2df-438c-ba40-2565-1f760e6d1edb@gmx.com> <9c2afb5f-e854-d743-3849-727f527e877b@gmx.com> <6e03129e-f8c8-a00b-2afe-97a82d06c11e@gmx.com> <7f8fde51-f920-06be-fdad-0cf59816adca@gmx.com> <362347bd-dca2-6074-c2c1-e453edd2a455@gmx.com> In-Reply-To: From: Robert Wyrick Date: Tue, 7 Sep 2021 17:20:52 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Next steps in recovery? To: Qu Wenruo Cc: Anand Jain , "linux-btrfs@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org Anything specific to address the dmesg error? On Tue, Sep 7, 2021 at 5:17 PM Qu Wenruo wrote: > > > > On 2021/9/8 =E4=B8=8A=E5=8D=884:47, Robert Wyrick wrote: > > Re-running check now shows: > > > > [1/7] checking root items (0:00:55 elapsed, > > 2649102 items checked) > > [2/7] checking extents (0:02:13 elapsed, > > 1116141 items checked) > > there is no free space entry for 18365358505984-18365358522368d, 130 > > items checked) > > there is no free space entry for 18365358505984-18366416814080 > > cache appears valid but isn't 18365343072256 > > there is no free space entry for 19764429062144-19764429078528d, 348 > > items checked) > > there is no free space entry for 19764429062144-19765502410752 > > cache appears valid but isn't 19764428668928 > > wanted bytes 49152, found 16384 for off 254016221675521 elapsed, 1534 > > items checked) > > wanted bytes 1058373632, found 16384 for off 25401622167552 > > cache appears valid but isn't 25401606799360 > > there is no free space entry for 28659399229440-28659399245824d, 2636 > > items checked) > > there is no free space entry for 28659399229440-28660413235200 > > cache appears valid but isn't 28659339493376 > > wanted offset 29154336178176, found 2915433616179200:33 elapsed, 2792 > > items checked) > > wanted offset 29154336178176, found 29154336161792 > > cache appears valid but isn't 29154334474240 > > there is no free space entry for 30899331825664-30899331842048d, 3585 > > items checked) > > there is no free space entry for 30899331825664-30900272234496 > > cache appears valid but isn't 30899198492672 > > there is no free space entry for 32134011568128-32134011584512d, 4474 > > items checked) > > there is no free space entry for 32134011568128-32135075332096 > > cache appears valid but isn't 32134001590272 > > wanted offset 33148689629184, found 3314868961280000:59 elapsed, 4963 > > items checked) > > wanted offset 33148689629184, found 33148689612800 > > cache appears valid but isn't 33148687613952 > > there is no free space entry for 34611225755648-34611225772032d, 6036 > > items checked) > > there is no free space entry for 34611225755648-34612197720064 > > cache appears valid but isn't 34611123978240 > > there is no free space entry for 37374972723200-37374972739584d, 8051 > > items checked) > > there is no free space entry for 37374972723200-37376042729472 > > cache appears valid but isn't 37374968987648 > > there is no free space entry for 37484494651392-37484494667776d, 8172 > > items checked) > > there is no free space entry for 37484494651392-37485564395520 > > cache appears valid but isn't 37484490653696 > > wanted bytes 49152, found 32768 for off 377572293017606 elapsed, 8381 > > items checked) > > wanted bytes 1065517056, found 32768 for off 37757229301760 > > cache appears valid but isn't 37757221076992 > > there is no free space entry for 38414356250624-38414356267008d, 9004 > > items checked) > > there is no free space entry for 38414356250624-38415424815104 > > cache appears valid but isn't 38414351073280 > > there is no free space entry for 41509957402624-41509957419008d, 11792 > > items checked) > > there is no free space entry for 41509957402624-41511022493696 > > cache appears valid but isn't 41509948751872 > > there is no free space entry for 42293815459840-42293815492608d, 12469 > > items checked) > > there is no free space entry for 42293815459840-42294887579648 > > cache appears valid but isn't 42293813837824 > > All free space cache related problems. > > You can just clear all v1 cache: > > $ btrfs check --clear-space-cache v1 > > Then it's also a good time to migrate to v2 cache, which is safer and > faster. > > # mount -o space_cache=3Dv2 > > Thanks, > Qu > > [3/7] checking free space cache (0:04:18 elapsed, 14910 > > items checked) > > [4/7] checking fs roots (0:00:26 elapsed, > > 108894 items checked) > > [5/7] checking csums (without verifying data) (0:00:03 elapsed, > > 12350321 items checked) > > [6/7] checking root refs (0:00:00 elapsed, 4 > > items checked) > > [7/7] checking quota groups skipped (not enabled on this FS) > > found 15729059287040 bytes used, error(s) found > > total csum bytes: 15313288548 > > total tree bytes: 18286706688 > > total fs tree bytes: 1791819776 > > total extent tree bytes: 229097472 > > btree space waste bytes: 1018811836 > > file data blocks allocated: 51587230765056 > > referenced 15627926974464 > > > > On Tue, Sep 7, 2021 at 11:17 AM Robert Wyrick wrote: > >> > >> Looks like I spoke too soon. > >> > >> I can now mount the FS readonly. > >> > >> I see this error in dmesg: > >> [58995.896369] CPU: 10 PID: 83845 Comm: btrfs-transacti Tainted: P > >> OE 5.11.0-27-generic #29~20.04.1-Ubuntu > >> [58995.896373] Hardware name: System manufacturer System Product > >> Name/PRIME X370-PRO, BIOS 0515 03/30/2017 > >> [58995.896376] RIP: 0010:btrfs_run_delayed_refs+0x1af/0x200 [btrfs] > >> [58995.896422] Code: 8b 55 50 f0 48 0f ba aa 48 0a 00 00 03 72 20 83 > >> f8 fb 74 3c 83 f8 e2 74 37 89 c6 48 c7 c7 50 7e 77 c0 89 45 d0 e8 96 > >> d4 4d d3 <0f> 0b 8b 45 d0 89 c1 ba 4c 08 00 00 4c 89 ef 89 45 d0 48 c7 > >> c6 c0 > >> [58995.896425] RSP: 0018:ffffb89a4a0dfdf8 EFLAGS: 00010282 > >> [58995.896428] RAX: 0000000000000000 RBX: ffffffffffffffff RCX: 000000= 0000000027 > >> [58995.896430] RDX: 0000000000000027 RSI: 00000000ffffdfff RDI: ffff96= 0fdf098ac8 > >> [58995.896432] RBP: ffffb89a4a0dfe40 R08: ffff960fdf098ac0 R09: ffffb8= 9a4a0dfbb8 > >> [58995.896434] R10: 0000000000000001 R11: 0000000000000001 R12: ffff96= 036a7d5378 > >> [58995.896435] R13: ffff960115028888 R14: ffff96036a7d5200 R15: 000000= 0000000000 > >> [58995.896437] FS: 0000000000000000(0000) GS:ffff960fdf080000(0000) > >> knlGS:0000000000000000 > >> [58995.896439] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > >> [58995.896441] CR2: 00005616936891e8 CR3: 000000010fe46000 CR4: 000000= 00003506e0 > >> [58995.896444] Call Trace: > >> [58995.896450] btrfs_commit_transaction+0x2c3/0xa80 [btrfs] > >> [58995.896500] ? start_transaction+0xd5/0x590 [btrfs] > >> [58995.896549] transaction_kthread+0x138/0x1b0 [btrfs] > >> [58995.896596] kthread+0x114/0x150 > >> [58995.896604] ? btrfs_cleanup_transaction+0x570/0x570 [btrfs] > >> [58995.896649] ? kthread_park+0x90/0x90 > >> [58995.896653] ret_from_fork+0x22/0x30 > >> [58995.896661] ---[ end trace c8ba04bdf2113cae ]--- > >> [58995.896664] BTRFS: error (device sdf) in > >> btrfs_run_delayed_refs:2124: errno=3D-17 Object already exists > >> [58995.896669] BTRFS info (device sdf): forced readonly > >> [58995.896672] BTRFS warning (device sdf): Skipping commit of aborted > >> transaction. > >> [58995.896674] BTRFS: error (device sdf) in cleanup_transaction:1939: > >> errno=3D-17 Object already exists > >> > >> Read-only is better than nothing, but what would be my next steps? > >> > >> On Tue, Sep 7, 2021 at 11:02 AM Robert Wyrick wrote: > >>> > >>> Ran a repair: > >>> > >>> $ sudo ./btrfs check --repair -p /dev/sda # I did NOT make install, > >>> just ran from the compiled directory > >>> enabling repair mode > >>> WARNING: > >>> > >>> Do not use --repair unless you are advised to do so by a developer > >>> or an experienced user, and then only after having accepted that no > >>> fsck can successfully repair all types of filesystem corruption. Eg. > >>> some software or hardware bugs can fatally damage a volume. > >>> The operation will start in 10 seconds. > >>> Use Ctrl-C to stop it. > >>> 10 9 8 7 6 5 4 3 2 1 > >>> Starting repair. > >>> Opening filesystem to check... > >>> Checking filesystem on /dev/sda > >>> UUID: 75f1f45c-552e-4ae2-a56f-46e44b6647cf > >>> [1/7] checking root items (0:00:59 elapsed, > >>> 2649102 items checked) > >>> Fixed 0 roots. > >>> Reset extent item (38179182174208) generation to 4057084elapsed, > >>> 1116143 items checked) > >>> No device size related problem found (0:02:22 elapsed, > >>> 1116143 items checked) > >>> [2/7] checking extents (0:02:23 elapsed, > >>> 1116143 items checked) > >>> cache and super generation don't match, space cache will be invalidat= ed > >>> [3/7] checking free space cache (0:00:00 elapsed) > >>> Deleting bad dir index [8348950,96,3] root 259 (0:00:25 elapsed, > >>> 106695 items checked) > >>> repairing missing dir index item for inode 834922400:26 elapsed, > >>> 108893 items checked) > >>> [4/7] checking fs roots (0:01:04 elapsed, > >>> 217787 items checked) > >>> [5/7] checking csums (without verifying data) (0:00:04 elapsed, > >>> 12350321 items checked) > >>> [6/7] checking root refs (0:00:00 elapsed, 4 > >>> items checked) > >>> [7/7] checking quota groups skipped (not enabled on this FS) > >>> found 15729059057664 bytes used, no error found > >>> total csum bytes: 15313288548 > >>> total tree bytes: 18286739456 > >>> total fs tree bytes: 1791819776 > >>> total extent tree bytes: 229130240 > >>> btree space waste bytes: 1018844959 > >>> file data blocks allocated: 51587230502912 > >>> referenced 15627926712320 > >>> > >>> I can now mount the filesystem successfully! Thank you for your help= . > >>> > >>> I do have some additional questions if you don't mind... > >>> I am already using RAID 1 to handle single disk outages. I assume > >>> things could have gone much worse and I could have lost the whole > >>> filesystem. Aside from backups (I know, I know), is there anything > >>> else I can do to prevent such issues or make them easier to recover > >>> from? Could this problem have been avoided/detected earlier? This > >>> wasn't a disk failure and according to memtest86+, it wasn't due to > >>> bad memory either.... I don't run scrubs very often. Should I? I > >>> guess the more general question is: What are the best practices for > >>> maintaining a healthy btrfs file system? > >>> > >>> Thanks again! > >>> > >>> On Mon, Sep 6, 2021 at 10:53 PM Qu Wenruo wr= ote: > >>>> > >>>> > >>>> > >>>> On 2021/9/7 =E4=B8=8B=E5=8D=8812:36, Robert Wyrick wrote: > >>>>> What exactly would i be disabling? I don't know what zoned does. > >>>> > >>>> The zoned device support. > >>>> > >>>> If you don't have any host-managed zoned device, there is no reason = you > >>>> would like to enable it. > >>>> > >>>> https://zonedstorage.io/introduction/ > >>>> > >>>> Thanks, > >>>> Qu > >>>> > >>>>> > >>>>> On Mon, Sep 6, 2021, 9:07 PM Anand Jain wro= te: > >>>>>> > >>>>>> On 07/09/2021 10:36, Robert Wyrick wrote: > >>>>>>> Trying to build latest btrfs-progs. I'm seeing errors in the con= figure script. > >>>>>>> > >>>>>>> $ cat /etc/os-release > >>>>>>> NAME=3D"Linux Mint" > >>>>>>> VERSION=3D"20.2 (Uma)" > >>>>>>> ID=3Dlinuxmint > >>>>>>> ID_LIKE=3Dubuntu > >>>>>>> PRETTY_NAME=3D"Linux Mint 20.2" > >>>>>>> VERSION_ID=3D"20.2" > >>>>>>> HOME_URL=3D"https://www.linuxmint.com/" > >>>>>>> SUPPORT_URL=3D"https://forums.linuxmint.com/" > >>>>>>> BUG_REPORT_URL=3D"http://linuxmint-troubleshooting-guide.readthed= ocs.io/en/latest/" > >>>>>>> PRIVACY_POLICY_URL=3D"https://www.linuxmint.com/" > >>>>>>> VERSION_CODENAME=3Duma > >>>>>>> UBUNTU_CODENAME=3Dfocal > >>>>>>> > >>>>>>> $ uname -a > >>>>>>> Linux bigbox 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 > >>>>>>> 15:58:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > >>>>>>> > >>>>>>> $ ./configure > >>>>>>> checking for gcc... gcc > >>>>>>> checking whether the C compiler works... yes > >>>>>>> checking for C compiler default output file name... a.out > >>>>>>> checking for suffix of executables... > >>>>>>> checking whether we are cross compiling... no > >>>>>>> checking for suffix of object files... o > >>>>>>> checking whether we are using the GNU C compiler... yes > >>>>>>> checking whether gcc accepts -g... yes > >>>>>>> checking for gcc option to accept ISO C89... none needed > >>>>>>> checking how to run the C preprocessor... gcc -E > >>>>>>> checking for grep that handles long lines and -e... /bin/grep > >>>>>>> checking for egrep... /bin/grep -E > >>>>>>> checking for ANSI C header files... yes > >>>>>>> checking for sys/types.h... yes > >>>>>>> checking for sys/stat.h... yes > >>>>>>> checking for stdlib.h... yes > >>>>>>> checking for string.h... yes > >>>>>>> checking for memory.h... yes > >>>>>>> checking for strings.h... yes > >>>>>>> checking for inttypes.h... yes > >>>>>>> checking for stdint.h... yes > >>>>>>> checking for unistd.h... yes > >>>>>>> checking minix/config.h usability... no > >>>>>>> checking minix/config.h presence... no > >>>>>>> checking for minix/config.h... no > >>>>>>> checking whether it is safe to define __EXTENSIONS__... yes > >>>>>>> checking for gcc... (cached) gcc > >>>>>>> checking whether we are using the GNU C compiler... (cached) yes > >>>>>>> checking whether gcc accepts -g... (cached) yes > >>>>>>> checking for gcc option to accept ISO C89... (cached) none needed > >>>>>>> checking whether C compiler accepts -std=3Dgnu90... yes > >>>>>>> checking build system type... x86_64-pc-linux-gnu > >>>>>>> checking host system type... x86_64-pc-linux-gnu > >>>>>>> checking for an ANSI C-conforming const... yes > >>>>>>> checking for working volatile... yes > >>>>>>> checking whether byte ordering is bigendian... no > >>>>>>> checking for special C compiler options needed for large files...= no > >>>>>>> checking for _FILE_OFFSET_BITS value needed for large files... no > >>>>>>> checking for a BSD-compatible install... /usr/bin/install -c > >>>>>>> checking whether ln -s works... yes > >>>>>>> checking for ar... ar > >>>>>>> checking for rm... /bin/rm > >>>>>>> checking for rmdir... /bin/rmdir > >>>>>>> checking for openat... yes > >>>>>>> checking for reallocarray... yes > >>>>>>> checking for clock_gettime... yes > >>>>>>> checking linux/perf_event.h usability... yes > >>>>>>> checking linux/perf_event.h presence... yes > >>>>>>> checking for linux/perf_event.h... yes > >>>>>>> checking linux/hw_breakpoint.h usability... yes > >>>>>>> checking linux/hw_breakpoint.h presence... yes > >>>>>>> checking for linux/hw_breakpoint.h... yes > >>>>>>> checking for pkg-config... /usr/bin/pkg-config > >>>>>>> checking pkg-config is at least version 0.9.0... yes > >>>>>>> checking execinfo.h usability... yes > >>>>>>> checking execinfo.h presence... yes > >>>>>>> checking for execinfo.h... yes > >>>>>>> checking for backtrace... yes > >>>>>>> checking for backtrace_symbols_fd... yes > >>>>>>> checking for xmlto... /usr/bin/xmlto > >>>>>>> checking for mv... /bin/mv > >>>>>>> checking for a sed that does not truncate output... /bin/sed > >>>>>>> checking for asciidoc... /usr/bin/asciidoc > >>>>>>> checking for asciidoctor... no > >>>>>>> checking for EXT2FS... yes > >>>>>>> checking for COM_ERR... yes > >>>>>>> checking for REISERFS... yes > >>>>>>> checking for FIEMAP_EXTENT_SHARED defined in linux/fiemap.h... ye= s > >>>>>>> checking for EXT4_EPOCH_MASK defined in ext2fs/ext2_fs.h... yes > >>>>>>> checking linux/blkzoned.h usability... yes > >>>>>>> checking linux/blkzoned.h presence... yes > >>>>>>> checking for linux/blkzoned.h... yes > >>>>>>> checking for struct blk_zone.capacity... no > >>>>>>> checking for BLKGETZONESZ defined in linux/blkzoned.h... yes > >>>>>> > >>>>>>> configure: error: linux/blkzoned.h does not provide blk_zone.capa= city > >>>>>> > >>>>>> > >>>>>>> > >>>>>>> --- > >>>>>>> > >>>>>>> Info on the file in question (linux/blkzoned.h): > >>>>>>> > >>>>>>> $ dpkg -S /usr/include/linux/blkzoned.h > >>>>>>> linux-libc-dev:amd64: /usr/include/linux/blkzoned.h > >>>>>>> > >>>>>>> $ dpkg -l linux-libc-dev > >>>>>>> Desired=3DUnknown/Install/Remove/Purge/Hold > >>>>>>> | Status=3DNot/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-= aWait/Trig-pend > >>>>>>> |/ Err?=3D(none)/Reinst-required (Status,Err: uppercase=3Dbad) > >>>>>>> ||/ Name Version Architecture Description > >>>>>>> +++-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>>>>> ii linux-libc-dev:amd64 5.4.0-81.91 amd64 Linux Kernel > >>>>>>> Headers for development > >>>>>>> > >>>>>>> > >>>>>>> So it appears that linux-libc-dev is way out-dated compared to my > >>>>>>> kernel. I don't know how to update it, though... there doesn't a= ppear > >>>>>>> to be a newer version available. > >>>>>> > >>>>>> You could disable the zoned. > >>>>>> > >>>>>> ./configure --disable-zoned > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>