Unsolved
This post is more than 5 years old
3 Posts
0
17008
January 5th, 2013 10:00
UNMap not working
We recently updated the firmware in our PS100 class SANs to 6.0.2 across the board. When attempting to use the VMware 5.1 vmkfstools -y command, nothing happens. The file is created as it says and it is immediately deleted within 1 minute, ending the command. Even when the filesize is over 300GB it still takes less that 1 minute. No differences in LUN size is reported in group manager or vCenter.
Is there something I am missing? Something that I have to turn on before this command will work? Reboot the host?? Does it work at all?
No Events found!
Mordock1
3 Posts
0
January 6th, 2013 09:00
No it is not being replicated, we have no replication in our environment. And of course the volume existed before the upgrade to 6.0.2. It would be utter stupidity for me to have to create new LUNs for an upgrade to work. It would mean moving 30TB of data, breaking all sorts of scripts that rely on datastore names and more pain than I can think of
Mordock2
1 Message
0
January 11th, 2013 17:00
Which brings up a good point which was actually my initial question. What could possibly be configured wrong. There are no configuration options available anywhere for unmap options. So just what could I possibly be missing? An interesting point that I noticed today is that when I use the command:
esxcli storage core device list
Every single LUN on my equallogic is reporting that it is thin provisioned, which is not correct. Only a handful out of 40 or 50 LUNs are set as thin provisioned.