Comments In Password And Group File Not Recognized - HP StorageWorks 4000s - NAS Release Note

Keep the following in mind when toggling between synchronous
and asynchronous writes:
1. When the caching setting for Services for NFS is set to
asynchronous writes (caching on), NFS clients may
incorrectly assume that all the writes were safely committed
to stable storage; the writes were only in the Server for NFS
cache.
2. For asynchronous writes: although Server for NFS informs
the NFS client that the data has been safely written to disk,
the data is still stored in cache and is waiting to be written to
disk. This could cause file corruption issues if, for example,
you lose your power supply to the Server for NFS server
while data is still in the cache. At this point, the NFS client
assumes that data that was lost was actually safely written to
disk.
3. With synchronous writes on (caching off), all write requests
are immediately committed to disk before a response is sent.
Although synchronous writes "on" does frequently slow
NFS file writes, it does improve the stability and data
integrity.

Comments in Password and Group file not recognized

Comments preceded by a "#" in the Password and Group file
will not be recognized when specifying the Password and Group
file for setting up the User and Group mappings of the NFS
protocol. If a Password or Group file is used with a comment,
the following error will be displayed in the WebUI: The user
list cannot be retrieved. Make sure the
password file is not corrupted and then try
again.
WARNING: Turn asynchronous writes on only if you are willing
to risk file corruption if any issue with the Services for NFS server
causes the cache to be lost (for example, if the system shuts down,
stops responding, loses its power supply, or experiences other
serious issues).
7