No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

N8500 NFS share attached to the linux vm, and the file system turned to be read-only accidentally

Publication Date:  2014-09-16 Views:  50 Downloads:  0
Issue Description
customer deployed vmware system and created some linux vm on vmware. and then created NFS file system on N8500 and attached to linux vm. and then found that sometimes the filesystem turned to be read-only.
Alarm Information
2014-04-30T14:46:32.178Z: [APDCorrelator] 1760645246360us: [esx.clear.storage.apd.exit] Device or filesystem with identifier [6a49e829-57c6ece2] has exited the All Paths Down state.
2014-04-30T14:46:32.179Z: [APDCorrelator] 1760692416666us: [vob.storage.apd.exit] Device or filesystem with identifier [4758327d-f5ecb9ab] has exited the All Paths Down state.
2014-04-30T14:46:32.179Z: [APDCorrelator] 1760645247532us: [esx.clear.storage.apd.exit] Device or filesystem with identifier [4758327d-f5ecb9ab] has exited the All Paths Down state.
2014-05-01T13:39:18.899Z: [APDCorrelator] 1843061343420us: [vob.storage.apd.start] Device or filesystem with identifier [6a49e829-57c6ece2] has entered the All Paths Down state.
2014-05-01T13:39:18.899Z: [APDCorrelator] 1843011967755us: [esx.problem.storage.apd.start] Device or filesystem with identifier [6a49e829-57c6ece2] has entered the All Paths Down state.
2014-05-01T13:39:25.842Z: [APDCorrelator] 1843068287110us: [vob.storage.apd.exit] Device or filesystem with identifier [6a49e829-57c6ece2] has exited the All Paths Down state.
2014-05-01T13:39:25.842Z: [APDCorrelator] 1843018911114us: [esx.clear.storage.apd.exit] Device or filesystem with identifier [6a49e829-57c6ece2] has exited the All Paths Down state.
2014-05-05T16:16:45.814Z: [APDCorrelator] 2198117773674us: [vob.storage.apd.start] Device or filesystem with identifier [89791be3-313be694] has entered the All Paths Down state.
Handling Process
1,check the alarm information from vmware about all path down, and record the time.
2,check the log in N8500 during those time.
3, couldn't find any abnormal information in N8500 log
4, check the log in vmware and search it from vmware website and found that it is similar with below bug


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

5, advised customer to install the vmware patch.
Root Cause
From the log in vmware, there are some alarm information about the All path down .however ,from the N8500 log, there is not any error information
Suggestions
Sometimes when customer reported the N8500, it is not our product and it is caused by the third party bug.

END