LKML Archive on
 help / Atom feed
* Possibe NFS mm problem: client page-in errors with ZFS Linux server
@ 2019-02-11 16:28 Martin Cracauer
  0 siblings, 0 replies; 1+ messages in thread
From: Martin Cracauer @ 2019-02-11 16:28 UTC (permalink / raw)
  To: linux-kernel

Folks.  I suspect that this isn't actually a ZFS bug but a general
memory manager problem.  I would appreciate input from mm folks.  I
parked the detailed bug report here for now:

Short story:

When running a ZFS on a Linux 4.19/4.20 NFS server the clients are
occasionally unsuccessful in perfectly normal page-in on mapped files.

Example: executable on NFS mounted filesystem.  Some executable-mapped
page is referenced.  The page is supposed to be retrieved on demand if
not resident yet.  This occasionally fails with recent Linux or ZoL

The semantics of the error are identical to what is legitimately
happening when you have a page fault in a NFS client mapped file after
that file has been unlinked on the server side.  Here it is happening
without the unlinking.

I suspect this might be a general Linux mm problem because I
cross-checked with a FreeBSD server with very similar ZFS code.
Although I cannot track when the error started appearing I know it is
about within the last 6 months and I read all commits to ZoL that
manage pages and couldn't see anything suspicious off-hand.  On the
other hand the errors do not appear when moving the server side file
tree to ext4fs.

The errors get more frequent with uptime of the server and are not
impressed by drop_caches or by trying to evict ZFS' own caches with
memory pressure.

Details with a line of reasoning why I blame the server and all other
info I am collecting:

Martin Cracauer <>

^ permalink raw reply	[flat|nested] 1+ messages in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-11 16:28 Possibe NFS mm problem: client page-in errors with ZFS Linux server Martin Cracauer

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ \
	public-inbox-index lkml

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox