This is on 12.0-RELEASE-p10+. Using TCP for all mounts. When I run
This is what happens when reading from a Linux client and running
The process is immediately aborted with the above error.
Here's what happens on write:
Anyone else running an extremely busy NFS server? Do you wait until a maintenance window to modify exports and reload mountd?
I don't think we ever saw this when we were running Linux, but then again, it doesn't happen that often. It could have been doing the same thing and we never noticed.
service mountd reload
(e.g. after editing /etc/exports) any in progress IO to the server gets completely disrupted. This really surprised me considering the exports() man page doesn't mention this at all which makes it seem like a non-service impacting thing to do:
Code:
The mountd(8) utility can be made to re-read the exports file by sending
it a hangup signal as follows:
/etc/rc.d/mountd reload
After sending the SIGHUP, check the syslogd(8) output to see whether
mountd(8) logged any parsing errors in the exports file.
This is what happens when reading from a Linux client and running
service mountd reload
on the server:
Code:
# dd if=/mnt/testing/testfile-READ.mp4 of=/dev/null iflag=direct
dd: error reading '/mnt/testing/testfile-READ.mp4': Permission denied
10950+0 records in
10950+0 records out
5606400 bytes (5.6 MB, 5.3 MiB) copied, 1.40982 s, 4.0 MB/s
The process is immediately aborted with the above error.
cp
does the same thing. I'm using dd
here to bypass the cache.Here's what happens on write:
Code:
# cp testfile.mp4 /mnt/testing/testfile-WRITE.mp4
cp: failed to close '/mnt/testing/testfile-WRITE.mp4': Permission denied
Anyone else running an extremely busy NFS server? Do you wait until a maintenance window to modify exports and reload mountd?
I don't think we ever saw this when we were running Linux, but then again, it doesn't happen that often. It could have been doing the same thing and we never noticed.
Last edited by a moderator: