From: Christian Kujau <lists@nerdbynature.de>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Anna Schumaker <anna.schumaker@netapp.com>,
Steve Dickson <steved@redhat.com>
Subject: Re: FS-Cache: Duplicate cookie detected
Date: Fri, 8 Mar 2019 15:25:09 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.999.1903081522160.21644@trent.utfs.org> (raw)
In-Reply-To: <alpine.DEB.2.21.999.1903081506320.21644@trent.utfs.org>
On Fri, 8 Mar 2019, Christian Kujau wrote:
> Running Linux v5.0 with this patch applied does indeed still produce the
> "Duplicate cookie detected" messages, but I only ever see wrq=0 when
> running nfstest_cache:
>
> https://paste.fedoraproject.org/paste/dkav0FQzYZxE9-V7GphjAQ
And again with the whole /proc/fs/fscache/stats output and better time
stamps: https://paste.fedoraproject.org/paste/hZtCPStJlqB1d9JXnTFndQ
C
--
BOFH excuse #5:
static from plastic slide rules
next prev parent reply other threads:[~2019-03-08 23:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 0:24 FS-Cache: Duplicate cookie detected Christian Kujau
2019-03-06 13:16 ` David Howells
2019-03-06 17:20 ` David Howells
2019-03-06 17:56 ` Christian Kujau
2019-03-08 14:49 ` David Howells
2019-03-08 17:57 ` Christian Kujau
2019-03-08 23:15 ` Christian Kujau
2019-03-08 23:25 ` Christian Kujau [this message]
2019-03-11 14:48 ` David Howells
2019-03-11 14:50 ` [PATCH 1/3] fscache: Fix cookie collision David Howells
2019-03-11 14:50 ` [PATCH 2/3] fscache: Add missing unhash David Howells
2019-03-11 14:50 ` [PATCH 3/3] fscache: Print cookie debugging information David Howells
2019-03-12 6:07 ` FS-Cache: Duplicate cookie detected Christian Kujau
2019-03-12 7:01 ` David Howells
2019-03-31 9:05 ` Christian Kujau
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=alpine.DEB.2.21.999.1903081522160.21644@trent.utfs.org \
--to=lists@nerdbynature.de \
--cc=anna.schumaker@netapp.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steved@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).