From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-6.9 regression tests fail
Date: Mon, 10 Jun 2024 10:23:41 +0930 [thread overview]
Message-ID: <53eb0a7d-3ec5-4719-b508-b5f366e3b4e5@gmx.com> (raw)
In-Reply-To: <2f8d2b44-8958-4312-bea2-8c53c2312c7c@gmail.com>
在 2024/6/10 09:23, Bruce Dubbs 写道:
> The convert and misc tests fail pretty early for me and I can't figure
> out why.
> The other btrfs tests complete normally.
>
> The significant output for convert-tests-results.txt is:
>
> ====== RUN CHECK mount -t btrfs -o loop
> /build/btrfs/btrfs-progs-v6.9/tests/test.img
> /build/btrfs/btrfs-progs-v6.9/tests/mnt
> mount: /build/btrfs/btrfs-progs-v6.9/tests/mnt: fsconfig system call
> failed: No such file or directory.
> dmesg(1) may have more information after failed mount system call.
> failed: mount -t btrfs -o loop
> /build/btrfs/btrfs-progs-v6.9/tests/test.img
> /build/btrfs/btrfs-progs-v6.9/tests/mnt
> test failed for case 003-ext4-basic
>
> dmesg gives me:
>
> [ 3807.421836] loop0: detected capacity change from 0 to 4194304
> [ 3807.421933] BTRFS: device fsid 4f1a8440-1a8f-45d1-9789-72080ddd9917
> devid 1 transid 7 /dev/loop0 (7:0) scanned by mount (3326)
> [ 3807.423458] BTRFS info (device loop0): first mount of filesystem
> 4f1a8440-1a8f-45d1-9789-72080ddd9917
> [ 3807.423469] BTRFS info (device loop0): using crc32c (crc32c-generic)
> checksum algorithm
> [ 3807.423477] BTRFS info (device loop0): using free-space-tree
> [ 3807.423911] BTRFS warning (device loop0): failed to read root
> (objectid=12): -2
That's objectid is for RST, which shouldn't even be enabled unless you
have enabled experimental features for btrfs-progs.
Mind to dump the superblock of that test image?
($BTRFS_PROGS_SOURCE/tests/test.img)
Thanks,
Qu
> [ 3807.424407] BTRFS error (device loop0): open_ctree failed
>
> My related kernel options are:
>
> CONFIG_BTRFS_FS=m
> CONFIG_BTRFS_FS_POSIX_ACL=y
> CONFIG_BTRFS_FS_RUN_SANITY_TESTS=y
> CONFIG_BTRFS_DEBUG=y
> CONFIG_BTRFS_ASSERT=y
> CONFIG_BTRFS_FS_REF_VERIFY=y
>
> and the btrfs kernel module is loaded.
>
> The kernel is version 6.9.3 on an AMD Ryzen 9 3900X
>
> I can format a btrfs partition and mount it.
>
> The system is linuxfromscratch so it may be something I've overlooked,
> but earlier versions worked OK.
>
> Any suggestions will be appreciated.
>
> -- Bruce Dubbs
> linuxfromscratch.org
>
next prev parent reply other threads:[~2024-06-10 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 23:53 btrfs-6.9 regression tests fail Bruce Dubbs
2024-06-10 0:53 ` Qu Wenruo [this message]
2024-06-10 7:12 ` Bruce Dubbs
2024-06-10 7:49 ` Qu Wenruo
2024-06-10 19:45 ` Bruce Dubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53eb0a7d-3ec5-4719-b508-b5f366e3b4e5@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=bruce.dubbs@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox