From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: Chuck Lever <chuck.lever@oracle.com>,
git@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: t0032 fails on NFS mounts
Date: Fri, 15 Mar 2024 01:35:27 +0100 [thread overview]
Message-ID: <ZfOXz81cpGZvq6Pq@tanuki> (raw)
In-Reply-To: <20240313072052.GC125150@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]
On Wed, Mar 13, 2024 at 03:20:52AM -0400, Jeff King wrote:
> +cc Patrick for reftable
>
> On Tue, Mar 12, 2024 at 11:10:29AM -0400, Chuck Lever wrote:
>
> > Unit test t0032 fails when run on an NFS mount:
> >
> > [vagrant@cel t]$ ./t0032-reftable-unittest.sh
> > not ok 1 - unittests
> > #
> > # TMPDIR=$(pwd) && export TMPDIR &&
> > # test-tool reftable
> > #
> > # failed 1 among 1 test(s)
> > 1..1
>
> The output for this test script is particularly unhelpful because it's
> not using our test harness at all, but just running a bunch of internal
> tests using a single program.
>
> Running with "-v" should give more details about what's failing.
>
> I set up a basic loopback server like:
>
> mkdir /mnt/{server,client}
> exportfs -o rw,sync 127.0.0.1:/mnt/server
> mount -t nfs 127.0.0.1:/mnt/server /mnt/client
>
> and then ran:
>
> ./t0032-reftable-unittest.sh --root=/mnt/client -v
>
> Looks like it fails at:
>
> running test_reftable_stack_compaction_concurrent_clean
> reftable/stack_test.c: 1063: failed assertion count_dir_entries(dir) == 2
> Aborted
>
> > v2.43.2 seems to work OK.
>
> For me, too. Bisecting shows the problem appearing in 4f36b8597c
> (reftable/stack: fix race in up-to-date check, 2024-01-18).
>
> -Peff
>
> PS That test seems to run ~20x slower on NFS versus directly on ext4.
> I'd expect a little overhead, but that's quite a bit.
Unless somebody else beats me to it I'll investigate this next week when
I'm back in the office. Thanks for the report and for digging into this
issue!
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-15 0:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 15:10 t0032 fails on NFS mounts Chuck Lever
2024-03-12 17:11 ` rsbecker
2024-03-21 15:50 ` Patrick Steinhardt
2024-03-13 7:20 ` Jeff King
2024-03-15 0:35 ` Patrick Steinhardt [this message]
2024-03-15 15:41 ` Junio C Hamano
2024-03-21 15:14 ` Patrick Steinhardt
2024-03-21 15:39 ` [PATCH] reftable: fix tests being broken by NFS' delete-after-close semantics Patrick Steinhardt
2024-03-21 17:35 ` Junio C Hamano
2024-03-22 15:15 ` Toon Claes
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=ZfOXz81cpGZvq6Pq@tanuki \
--to=ps@pks.im \
--cc=chuck.lever@oracle.com \
--cc=git@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.