Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp4184258rwd; Tue, 23 May 2023 04:33:26 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7dl7yW6p62vKdvbTo8rlPHq55rzP0v3K5+r9SceD+PlNrtPwq/rgpQ7HXb7bOm+3/1WmXe X-Received: by 2002:a05:6a20:5486:b0:100:ba96:e5e7 with SMTP id i6-20020a056a20548600b00100ba96e5e7mr15586420pzk.18.1684841606247; Tue, 23 May 2023 04:33:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684841606; cv=none; d=google.com; s=arc-20160816; b=lv4dWGk+DKBNy7fZxVT56WwHNCWFNLN+lgIy8iHwjsK+eP1fM6Yp3Sn7ufgz+4C6mB jyRsg94LLL9lzzDJSPBHfNx4ajG02l0uJxVlH8iUAeZ55BQjUW1fW11zQ36e8N9wqwoi nMTjRTUPhMJfVGxSuo9ft1IJ3mlTtykO7x09neBf3yZt83kprQTawYh2zWu0NfYIFcIk HzkBMnxl9oAp/YMrNAnboHaeNa//X5CXYiq057QQdr97wR0ohnhALrWic+VprNp4ZiM6 px3ztiIoGIUPmVzKmdE58XHZ1xiHOsh33++LMYhLTVOi9W3XFXEvdPDoevmBgqfsSNKD IkfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=0zNJf1ZxIlrz72iFEKXCdEhtPieGC/o/YCVkxcPf5Cw=; b=EFkEpnJmX3fRM3yfNXOtwoI6D6/ZLRN2Dwii9Db9N4UO3i8gCIPcsKe9jRhwMKjI2v 7/sAK/zW4jMD7k6rbhP61mZK7s699i/YUu47Rltj38/77U4Tte0NJKGwo7Jp2T+C1Cen DYoC3Pa9GYrgN4ZGX2CUh1EJtpBnkPb9ykWAyxh9yPqi9RhAiUpiDaqnHSdAuXeQ7RxJ ZuQ0w6nWmraeQ+r1RT33EDJtmnNL+PrZ+fW3OIDa9S1Bj51Th9IPvu3N5bXuscvJJvMn FQipot1YA9bEltS+pIJYcmyytwMFaL7f2/CStxxwFiNnbbFVHMFACtKmi4TG1QnJUcmH wbEg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b="qqA/K+I9"; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w14-20020aa7954e000000b00643bc9d1245si1210936pfq.314.2023.05.23.04.32.51; Tue, 23 May 2023 04:33:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b="qqA/K+I9"; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231410AbjEWLSY (ORCPT + 99 others); Tue, 23 May 2023 07:18:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49122 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229653AbjEWLSX (ORCPT ); Tue, 23 May 2023 07:18:23 -0400 Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 60C82C4 for ; Tue, 23 May 2023 04:18:22 -0700 (PDT) Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-96f50e26b8bso973903666b.2 for ; Tue, 23 May 2023 04:18:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684840700; x=1687432700; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0zNJf1ZxIlrz72iFEKXCdEhtPieGC/o/YCVkxcPf5Cw=; b=qqA/K+I9B6NMGuLEnngDkghGJwZ4m++6WJoa0t5lTvqmEn+ua7ok+RIH2q19DhyhGA cG4ObwfD7/eO0Dwb0r9mHsQ8SLxkSsNx4naXAA1Ch3jClI9WMxzR42PkMMMD+0bjonC5 JvL1rlaE0DGa7kODDQjxyENLWtOi4nd8WtU5IrrJiAs9a4cpaviv+/Eu/4fi+nFS4pTu Z28Y/+wdib8voI+cgFmZg77zGXVBvyjjEPEDfD2/4PT+mxBnKbqy2QNf64oNwgLkAsTw rsfyyBFOdZ3aqrKzuM47ataM6u2xXYct/4eaBhvOmSubxXW79JWysFTRKemYiNak+Jcw yp6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684840700; x=1687432700; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0zNJf1ZxIlrz72iFEKXCdEhtPieGC/o/YCVkxcPf5Cw=; b=Y+fyLv99jVXw0/29e4gXyBTDlqcnRGjjm58F2NDdSJQi3mW21JCL9fRuWfTV7e51gc Xohwq5qlUufSUV4rY+6xf5t5R+FUFV09HWGbbysMGYs/h63Zit28RrWiJ8bSUmuCtwzv Ofcx+N367KdOIRkn+ViwpJa5h+fR1SfOrC67gMgwjG2IsT5uQ5E8vHoPgZFe3ruqscFC zIX/ew8L9t1iD/1lF9sk65+JwVVj+al2MQFny1OPheI/huK+TPP4k0L7LvxsfZM+zgr+ 8wLkczFLtith+ECs21f3g9Krb8RlgV9ch/rjOBKW55Ws2PThjXBZyIuvF7ydLCQAVSjO /sbw== X-Gm-Message-State: AC+VfDyM/0wixDjD8vmT2F2AfLXd50461LT8cLRapU3arHx4ri3Feu4S MZq9aZ7iXashCnTNv4zwHgaHQ1QoH77zIxOsM8BEtp2x/FQ= X-Received: by 2002:a17:906:5d04:b0:95e:d74b:d171 with SMTP id g4-20020a1709065d0400b0095ed74bd171mr13436332ejt.28.1684840699474; Tue, 23 May 2023 04:18:19 -0700 (PDT) MIME-Version: 1.0 References: <1744185.1684489212@warthog.procyon.org.uk> In-Reply-To: <1744185.1684489212@warthog.procyon.org.uk> From: Chris Chilvers Date: Tue, 23 May 2023 12:18:08 +0100 Message-ID: Subject: Re: [Linux-cachefs] [BUG] fscache writing but not reading To: David Howells Cc: linux-nfs@vger.kernel.org, linux-cachefs@redhat.com, brennandoyle@google.com, Benjamin Maynard Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Fri, 19 May 2023 at 10:40, David Howells wrote: > > Chris Chilvers wrote: > > > While testing the fscache performance fixes [1] that were merged into 6.4-rc1 > > it appears that the caching no longer works. The client will write to the cache > > but never reads. > > Can you try reading from afs? You would need to enable CONFIG_AFS_FS in your > kernel if it's not already set. > > Install kafs-client and do: > > systemctl enable afs.mount > md5sum /afs/openafs.org/software/openafs/1.9.1/openafs-1.9.1-doc.tar.bz2 > cat /proc/fs/fscache/stats FS-Cache statistics Cookies: n=13 v=7 vcol=0 voom=0 Acquire: n=13 ok=13 oom=0 LRU : n=1 exp=0 rmv=0 drp=0 at=2833 Invals : n=0 Updates: n=0 rsz=0 rsn=0 Relinqs: n=0 rtr=0 drop=0 NoSpace: nwr=0 ncr=0 cull=0 IO : rd=0 wr=18 RdHelp : RA=18 RP=0 WB=0 WBZ=0 rr=0 sr=0 RdHelp : ZR=1 sh=0 sk=0 RdHelp : DL=18 ds=18 df=0 di=0 RdHelp : RD=0 rs=0 rf=0 RdHelp : WR=18 ws=18 wf=0 This was on an instance that was only just created, so the cache was initially unused (all the counters were 0). > umount /afs/openafs.org > md5sum /afs/openafs.org/software/openafs/1.9.1/openafs-1.9.1-doc.tar.bz2 > cat /proc/fs/fscache/stats FS-Cache statistics Cookies: n=13 v=7 vcol=0 voom=0 Acquire: n=26 ok=26 oom=0 LRU : n=1 exp=1 rmv=0 drp=0 at=467 Invals : n=0 Updates: n=0 rsz=0 rsn=0 Relinqs: n=13 rtr=0 drop=13 NoSpace: nwr=0 ncr=0 cull=0 IO : rd=18 wr=18 RdHelp : RA=36 RP=0 WB=0 WBZ=0 rr=0 sr=0 RdHelp : ZR=1 sh=0 sk=0 RdHelp : DL=18 ds=18 df=0 di=0 RdHelp : RD=18 rs=18 rf=0 RdHelp : WR=18 ws=18 wf=0 Looks like the cache is working fine with AFS. The second md5sum seemed a lot quicker than the first.