adding new NAS volume append (1) to end

[sirreepicheep]

I was having a problem with a volume being unavalable to one host.  After trying to reenable the volume I decided to delete the volume from the host and re-add it.  I deleted the volume using:

esxcfg-nas -d antelope2

Then ran esxcfg-nas -l to ensure the volume was no longer listed.  After this I added the volume back to the host, but instead of getting volume 'antelope2' I get volume 'antelope2(1).

~ # esxcfg-nas -a antelope2 -o 192.168.5.29 -s /store

Connecting to NAS volume: antelope2

antelope2 created and connected.

~ # esxcfg-nas -l

NAS03NIC2 is /store from 192.168.5.30 mounted available

antelope is /store from nas02 mounted available

antelope2 (1) is /store from 192.168.5.29 mounted available

I tried to rename the volume in the vSphere Client, but get a popup message that says "The name 'antelope2' already exist."

How do I completely removed the original volume 'antelope2' and re-add the volume back as 'antelope2'?  I see nothing in the cli or vSphere Client that indicate the volume still exist other then the fact that I cannot create the volume.

Thanks for any assistance you can provide.

[zXi_Gamer]

You have to escape the characters of "("

Try giving

esxcfg-nas -d antelope2\(1\)

[zXi_Gamer]

And once removed, try adding it back using antelope2 name

[sirreepicheep]

I have already done that.  I can remove to new share using

esxcfg-nas -d antelope2\ \(1\)                         (it puts a space before the appended (1))

then re-add using same command as above, but get the exact same results - the appened (1).

[zXi_Gamer]

It seems that the esx.conf file is not updated or another operation is carried on which might still have the lock..

[sirreepicheep]

At this time I have nothing on the host so I removed the volume and rebooted, figuring if a file was locked a reboot would take care of it.  After reboot I tried to add the volume again with the exact same results.  I checked the esx.conf files to see if the old volume as in the file and it is not.  Any other files that could be hanging on to the antelope2 volume not allowing it to be re added?

Commands/output ran post reboot:

~ # esxcfg-nas -a antelope2 -o 192.168.5.29 -s /store

Connecting to NAS volume: antelope2

antelope2 created and connected.

~ #

~ #

~ # esxcfg-nas -l

NAS03NIC2 is /store from 192.168.5.30 mounted available

antelope is /store from nas02 mounted available

antelope2 (1) is /store from 192.168.5.29 mounted available

~ #

~ #

~ # less /etc/vmware/esx.conf |grep antelope2

/nas/antelope2 (1)/enabled = "true"

/nas/antelope2 (1)/host = "192.168.5.29"

/nas/antelope2 (1)/readOnly = "false"

/nas/antelope2 (1)/share = "/store"

~ #

[zXi_Gamer]

Alrighty, lets rule out the usual suspects.

1. Is the ESX added as a part of any other Vcenter?, if yes, remove the nas volume from there and remove the host [just to confirm.] and try adding it bak

2. http://communities.vmware.com/thread/281232?start=0&tstart=0

[sirreepicheep]

Ok, it is working now.  Turned out to be a DNS issue.  I had seen the discussion zXi_Gamer linked to, did not see anything that really seemed to apply. The discussion mentioned DNS, which I did not think applied since I was using the IP.  I decided to look at the DNS setup and their were two entries for the devices DNS name with different IP addresses.  Removed the entry not needed and everything worked.  Not sure why DNS would even come into play since I was using the IP but for whatever reason it did.

Thanks for all you help zXi_Gamer.

[zXi_Gamer]

most welcome :smileyhappy:

[Rubeck]

After removing it, could you try a esxcfg-nas -a antelope2 -o 192.168.5.29 -s /store/

/Rubeck