NFS V4.1 Server Range Lock Allows Write by a Client When a Lock is Held by Another Client.
(Doc ID 2733640.1)
Last updated on JANUARY 27, 2025
Applies to:
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]Oracle ZFS Storage ZS4-4 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS7-2 High End - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage Appliance Racked System ZS7-2 Mid-Range - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-4 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)
When using NFS v4.1 with Red Hat Fail Over Cluster for quorum file, each node is able to write to the same range in the file. This should not be allowed. The active node should control the range lock and prevent the standby node from writing to the range. Due to a bug in NFS v4.1 server the range lock issued by the primary node does not always lock the range.
Symptoms
Red Hat Cluster would go Active/Active. This is an Active/Passive cluster technology. Going Active/Active can cause unreliable cluster operation and data corruption.
Changes
Changing client NFS mount option to NFS v4.1
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| Goal |
| References |