Just to be clear, the exadata is writing to the VNX5400 NFS share, correct? If so, check the UID/GID that exadata is using. If it is writing as root, ensure that the NFS export has the right security for that UID.
When you setup rw and root access to your exadata, did you specify a host name, rather than an IP address? If so, check your DNS settings and make sure the datamovers are able to resolve the hostname correctly.
Another thing to look at, if you specified an IP address in the RW and root access, is to make sure you have the correct IP.
Dear All thanks for help, the problem is exadata connect to vnx using different ip address so when I add the outgoing ip address to root and read write host access it's can write smoothly...thank you
Rainer_EMC
4 Operator
•
8.6K Posts
0
August 19th, 2015 02:00
Open a service request and provide network traces
umichklewis
3 Apprentice
•
1.2K Posts
0
August 19th, 2015 10:00
Just to be clear, the exadata is writing to the VNX5400 NFS share, correct? If so, check the UID/GID that exadata is using. If it is writing as root, ensure that the NFS export has the right security for that UID.
Let us know if that helps!
Karl
Rainer_EMC
4 Operator
•
8.6K Posts
0
August 19th, 2015 11:00
An error about read-only file system sounds more like a config issue not exporting to the correct client IP as read-write
storagtetalk
1 Rookie
•
53 Posts
0
August 21st, 2015 10:00
When you setup rw and root access to your exadata, did you specify a host name, rather than an IP address? If so, check your DNS settings and make sure the datamovers are able to resolve the hostname correctly.
Another thing to look at, if you specified an IP address in the RW and root access, is to make sure you have the correct IP.
aldyth_m
8 Posts
0
August 23rd, 2015 18:00
Dear All thanks for help, the problem is exadata connect to vnx using different ip address so when I add the outgoing ip address to root and read write host access it's can write smoothly...thank you