Linux NFS development
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Chris Chilvers <chilversc@gmail.com>
Cc: dhowells@redhat.com, linux-nfs@vger.kernel.org,
	linux-cachefs@redhat.com, brennandoyle@google.com,
	Benjamin Maynard <benmaynard@google.com>
Subject: Re: [Linux-cachefs] [BUG] fscache writing but not reading
Date: Fri, 19 May 2023 10:40:12 +0100	[thread overview]
Message-ID: <1744185.1684489212@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAAmbk-f_U8CPcTQM866L572uUHdK4p5iWKnUQs4r8fkW=6RW9g@mail.gmail.com>

Chris Chilvers <chilversc@gmail.com> 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
	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

David


  parent reply	other threads:[~2023-05-19  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 15:42 [BUG] fscache writing but not reading Chris Chilvers
2023-05-16 19:28 ` [Linux-cachefs] " David Wysochanski
2023-05-18 20:20   ` Chris Chilvers
2023-05-19 11:53     ` David Wysochanski
2023-05-24 16:13       ` David Wysochanski
2023-05-19  9:40 ` David Howells [this message]
2023-05-23 11:18   ` Chris Chilvers
2023-05-23 14:15     ` David Wysochanski

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=1744185.1684489212@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=benmaynard@google.com \
    --cc=brennandoyle@google.com \
    --cc=chilversc@gmail.com \
    --cc=linux-cachefs@redhat.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