Failed write command to write-quiesced partition

ESX box may see below errors, due to some storage box side issues.
you may observe mostly on all the ESX hosts of the VC Cluster - kind of below errors.

ALERT: ScsiDeviceIO: 2352: Failed write command to write-quiesced partition naa.50a9800064656c5a4a5a654e35594123:1 
Extract from /var/log/vmkernel - below
/var/log/vmkernel cpu21:4342)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4102ff3ac040) to  NMP device "naa.50a9800064656c5a4a5a654e35594123" failed on physical path "vmhba1:C0:T1:L1" H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

/var/log/vmkernel cpu21:4342)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:
NMP device "naa.50a9800064656c5a4a5a654e35594123" state in doubt; requested fast path state update...

/var/log/vmkernel cpu21:4342)ScsiDeviceIO: 1672: Command 0x2a to
device "naa.50a9800064656c5a4a5a654e35594123" failed H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

Solution
There may be nothing much on ESX side to resolve these errors, Involve your storage vendor to solve this - refer at below VMware KB for more details.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2009482

How to identify your DATA STORE name from NAA ID - Example below

# esxcfg-scsidevs -m | grep -i "naa.50a9800064656c5a4a5a654e35594123"

How to identify you LUN ID from Data Store Name
Select ESX at VC - configuration - storage - right click - Properties

Re-Connect NFS Datastore without Restarting ESX Host (in case NFS Physical connection is lost & restored)

Try below VMware KB  or another work around below..
(Ensure vmkping x.x.x.x) - where x.x.x.x is your NAS IP - is pinging

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005057


Another workaround - below

NFS is a great storage solution within a VMware vSphere environment. But when the connection to the NFS server is lost, you’re in big trouble. In most circumstances some virtual machines are still connected to the NFS Datastore and since it’s in use, you cannot delete and recreate it. I’ve tried this by using the vSphere Client and trough the command line but didn’t succeed. In the end there’s no other alternative than rebooting the ESX host, or is there… If you want to find out how to remount an NFS Datastore you may watch below video. By Eric Sloof

Actual Trick is - NFS data store IP was x.x.x.x, he created a host name (using /etc/hosts file or DNS or alias host name on DNS) to fool the vCenter, then added host name when adding NFS source. vCenter thinks it's getting NFS from different Source..

May be it's a little dragging video, wait till end of video to see the insight