Page MenuHomeFreeBSD

update mount_nfs(8) man page for uses of the oneopenown option
ClosedPublic

Authored by rmacklem on Jan 17 2021, 9:40 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Oct 30, 5:22 PM
Unknown Object (File)
Oct 4 2024, 11:26 AM
Unknown Object (File)
Oct 3 2024, 5:34 AM
Unknown Object (File)
Oct 2 2024, 6:13 PM
Unknown Object (File)
Oct 1 2024, 9:21 AM
Unknown Object (File)
Oct 1 2024, 4:04 AM
Unknown Object (File)
Sep 27 2024, 1:47 PM
Unknown Object (File)
Sep 25 2024, 9:46 PM
Subscribers

Details

Summary

A recent email discussion indicated that a large
accumulation of NFSv4 Opens was occurring on
a mount. This appears to have been caused by a
shared library within the mount being used by
several processes, such that there is always at
least one of these processes running.
A new Open was created by each process and
were not closed, since all the Opens were never
closed. This is alleviated by using the
"oneopenown" mount option.

This man page update attempts to indicate the
use of "oneopenown" for this case.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

rmacklem created this revision.
0mp added a subscriber: 0mp.

Seems fine apart from one typo and one suggestion I've left as a comment.

sbin/mount_nfs/mount_nfs.8
229
230

Just a suggestion. Perhaps the sentence can start like this: "A common case for an accumulation of Opens is a shared library...".

It might be that I am just not familiar enough with NFS to fully understand the content.

This revision is now accepted and ready to land.Jan 17 2021, 10:36 PM

Marked comments as done.