IBM AIX 7.3 – Common Problem 123 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

NFSv4 mounted files show owner ‘nobody:nobody’ on client.

Environment & Reproduction

Domain mismatch in /etc/nfs/local_domain between server/client.

Root Cause Analysis

nfsrgyd cannot map UID to user name across domains.

Quick Triage

Run chnfsdom and cat /etc/nfs/local_domain on both ends.

Step-by-Step Diagnosis

Check lssrc -s nfsrgyd and /var/adm/ras/nfs4cl.log.

Solution – Primary Fix

Set domain with chnfsdom example.com on both, then refresh -s nfsrgyd.

Solution – Alternative Approaches

Switch mount to NFSv3 as a fallback via -o vers=3.

Verification & Acceptance Criteria

ls -l on mount shows correct user/group names.

Rollback Plan

Revert domain change if it breaks Kerberos principal mapping.

Prevention & Hardening

Sync NIS/LDAP UID maps and document NFS domain.

Related Errors & Cross-Refs

Pairs with Kerberos cross-realm trust issues.

Related tutorial: View the step-by-step tutorial for aix-7.3.

View all aix-7.3 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

IBM Docs: NFSv4 identity mapping.