So, did you compare iostat data for the following 2 scenarios?
1) AIX NFS server receiving writes from an NFS client over the network
2) Local AIX process writing data to the AIX file system (preferably from a local FS like /tmp)
As I stated earlier, your iostat data shows average IO size of only ~40KB to disk - but that is averages - << even the default 0x40000 (256KB) max_transfer.
Of interest here is if IO rates, IO transfer sizes, IO service times, service queue full events are dramatically different between the 2 test cases.
If you are advantageous, do a test with "dio" mount for that file system and evaluate IO sizes,..., behavior, as well. This will take JFS2 file cache out of the picture.
I assume you are monitoring during your tests if / how the JFS2 file cache is utilized in your testing?
------------------------------
Ralf Schmidt-Dannert
------------------------------
Original Message:
Sent: Fri October 11, 2024 11:42 AM
From: jack smith
Subject: NFS specific disk slow writes
> why would max_transfer have to be increased to 0x100000 == 1MB?
As mentioned already: "Otherwise read and write speeds were very bad".
For example at the default 0x40000 the transfer speeds were stuck at 20mb/s. Local usage that is, not over the network.
> are we talking "spinning disk" at the backend?
As mentioned already: "Toshiba HDD".
> Large file write or "many small" writes?
Single files between 2MB and 200MB. One file at a time, not a bunch of files with a single command/transfer.
> taking NFS / network out of the picture?
As mentioned already: "If AIX is the NFS client getting stuff from another NFS server, writing to the disk in question is fine. So the problem only affects writing to the disk in question from an NFS client.".
So to rephrase, after setting max_transfer to 0x100000 or higher, everything worked fine except for writes from NFS clients as described.
> How is the exported file system mounted in the AIX NFS server?
As a local LV with: rw,noatime,log=NULL
> Are there any errors in AIX error log on the AIX NFS server?
None.
For the record, this is an AIX specific problem. Using the disk in question with a SUSE LPAR on the same machine works fine by default. No need for any settings.