From: David Howells <dhowells@redhat.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
Anna Schumaker <anna.schumaker@netapp.com>,
Steve Dickson <steved@redhat.com>
Subject: Re: FS-Cache: Duplicate cookie detected
Date: Tue, 12 Mar 2019 07:01:48 +0000 [thread overview]
Message-ID: <8939.1552374108@warthog.procyon.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.999.1903112235120.21644@trent.utfs.org>
Christian Kujau <lists@nerdbynature.de> wrote:
> My /usr/local/src mount was mounted with vers=4.2 (default), while
> nfstest_cache was mounting its test-mount with vers=4.1! Apart from the
> different rsize/wsize values, the version number stood out. And indeed,
> when I mount my regular NFS mount /usr/local/src with vers=4.1, the
> "duplicate cookie" is no longer printed.
Yeah - NFS superblocks are differentiated by a whole host of parameters,
including protocol version number, and caches aren't shared between
superblocks because this introduces a tricky coherency problem.
The issue is that NFS superblocks to the same place do not currently manage
coherency (inode attributes, data) between themselves, except via the server.
However, if "fsc" isn't given on the mount commandline, the superblock
probably shouldn't get a server-level cookie if we can avoid it.
David
next prev parent reply other threads:[~2019-03-12 7:01 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
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 [this message]
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=8939.1552374108@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--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).