Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp6132207imb; Fri, 8 Mar 2019 09:57:56 -0800 (PST) X-Google-Smtp-Source: APXvYqwCnH4rHuQ55B9/G5JINS1NMAh2w4yoaj6mz4DjQ65PhSVE82qzlIKYMqKuaEZSSCFb/wiR X-Received: by 2002:a17:902:b58c:: with SMTP id a12mr20104730pls.102.1552067876504; Fri, 08 Mar 2019 09:57:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1552067876; cv=none; d=google.com; s=arc-20160816; b=ZoGSFkeTDHanWIq+ZKOjEJXJe6jUV1IhXn5kvo4fuyjwyuWqTFalp5y+aULGJ49Hp6 A3QibiwLqO2wO0bUB97JXyQR9fqPkb7owGd4ArAH942tQBgeRkpnCOxE/+QW7KaJof+M yKgS56D00JH0S60P6x9Z3NanUxQlIRWAX58QBEGVqVxXnGvZKrq087rZM68S5aIB+2zK IIaCMd/LEGjQEk2fZ3YMfyMbpkwgaaAIhk/Gv89bC5NZOY3keIetAXxtSACSckiGmHe6 OAuLPPvvgilUvkONzeQCI+SPJleXZCCOrQLQbEWaAnB8IQwTKyncWuPAh9InsEhQmvF1 BwNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=jLy/V9Jz985rk67Z4Kr9g/zQElOmf5YXEOOqzJovicg=; b=C2IL5MaF3y/Oym6eF06Icyx4j5lm8kTkmvXk2dmOFEIq2QUbc7mSShqOUjBVcMZ4xF Tx1aSvCd7uD6b6hMy7+YE9QgFSNgbjEWWixX4wFWI5b1+SeR5GSMJ+d6TsbDvrbIMYL8 RVkg3zUnbWk1Ga9vcr1U8x+wUt1c8rglfwemJFZghU5vpvANfKgzSquzxHEg26y5ATgi AdOXL/vRULuYIyJHEi7ehLI1cvF0snNYcHk3DGgi9eKx/qkGdRwC0Y9JibawpvuDcya1 Ic35ruzaGzLW37kY/71HxH7Se/KOfg1a69AnUC7kFNOoyEc6UO9osvU2h2uFhGgLv6k5 cYyQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 72si7699038ple.250.2019.03.08.09.57.41; Fri, 08 Mar 2019 09:57:56 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726946AbfCHR5P (ORCPT + 99 others); Fri, 8 Mar 2019 12:57:15 -0500 Received: from trent.utfs.org ([94.185.90.103]:42110 "EHLO trent.utfs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726494AbfCHR5P (ORCPT ); Fri, 8 Mar 2019 12:57:15 -0500 Received: from localhost (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by trent.utfs.org (Postfix) with ESMTPS id 16B316427B; Fri, 8 Mar 2019 18:57:13 +0100 (CET) Date: Fri, 8 Mar 2019 09:57:13 -0800 (PST) From: Christian Kujau To: David Howells cc: linux-kernel@vger.kernel.org, Anna Schumaker , Steve Dickson Subject: Re: FS-Cache: Duplicate cookie detected In-Reply-To: <17155.1552056554@warthog.procyon.org.uk> Message-ID: References: <22096.1551878195@warthog.procyon.org.uk> <10106.1551892803@warthog.procyon.org.uk> <17155.1552056554@warthog.procyon.org.uk> User-Agent: Alpine 2.21.999 (DEB 277 2018-05-20) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 8 Mar 2019, David Howells wrote: > > $ mount | grep nfs4 > > nfs:/usr/local/src on /usr/local/src type nfs4 (ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.56.139,local_lock=none,addr=192.168.0.115) > > > > ...so FS-Cache ("fsc") isn't even used here. > > Interesting. Can you do: > > cat /proc/fs/nfsfs/volumes That seems to confirm the mount options, fsc is disabled: # cat /proc/fs/nfsfs/volumes NV SERVER PORT DEV FSID FSC v4 c0a80073 801 0:46 1cfd45bf1921474d:a795870ea80f5ff7 no > See the attached for a patch that helps with certain kinds of collision, > though I can't see that it should help with what you're seeing since the > RELINQUISHED flag isn't set on the old cookie (fl=222, but 0x10 isn't in > there). You can monitor the number of waits by looking in > /proc/fs/fscache/stats for the: > > Acquire: n=289166 nul=0 noc=0 ok=286331 nbf=2 oom=0 wrq=23748 Ah, the wrq= field gets only introduced by this patch. OK, I'll see if I can build a test kernel with that and will report back. Thanks for looking in to this, Christian. -- BOFH excuse #290: The CPU has shifted, and become decentralized.