From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: reservation errors during fstests on pNFS block
Date: Fri, 14 Jun 2024 09:38:16 -0700 [thread overview]
Message-ID: <Zmxx-H2KrT5QpJ-g@infradead.org> (raw)
In-Reply-To: <34F83726-2A28-4E29-A40E-A01BED7744EC@oracle.com>
On Fri, Jun 14, 2024 at 02:46:49PM +0000, Chuck Lever III wrote:
> I've finally gotten kdevops and pNFS block to the point where
> it can run fstests smoothly with an iSCSI target. I'm seeing
> error messages on occasion in the system journal. This set is
> from generic/069:
Reservation means another node has an active reservation on that LU.
Either you did another previous attempt that fail and let the
reservation linger, or something else in the system claimed it.
> But note that generic/069 is recorded as passing without error.
When pNFS layout access fails we fall back to normal access through the
MDS, so this is expected.
Is generic/069 that first test that failed when doing a full xfstests
run? Do you see LAYOUT* ops in /proc/self/mountstats for the previous
tests?
next prev parent reply other threads:[~2024-06-14 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 14:46 reservation errors during fstests on pNFS block Chuck Lever III
2024-06-14 16:38 ` Christoph Hellwig [this message]
2024-06-14 17:46 ` Chuck Lever III
2024-06-14 18:26 ` Christoph Hellwig
2024-06-14 18:33 ` Chuck Lever III
2024-06-14 18:34 ` Christoph Hellwig
2024-06-15 18:09 ` Chuck Lever III
2024-06-17 5:38 ` Christoph Hellwig
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=Zmxx-H2KrT5QpJ-g@infradead.org \
--to=hch@infradead.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@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