piseema's Posts

when we do "esxcli storage core adapter rescan" , does the host send SCSI inquiry command as part of it? 
Yes, absolutely, we are in process of changing the policy to FTT=1. It is all flash cluster and thanks for the great advise, appreciate it.
Hi Bob, Thanks for responding. yes, a physical drive failure and unfortunately no backup so data loss
vSAN 6.5 4 Node Cluster Each node has 1 SSD and 2 Capacity disk FTT=0 RAID=1 Had a disk failure in node 4, Did we lose data? or with RAID=1 we have the mirred it to another host? Please he... See more...
vSAN 6.5 4 Node Cluster Each node has 1 SSD and 2 Capacity disk FTT=0 RAID=1 Had a disk failure in node 4, Did we lose data? or with RAID=1 we have the mirred it to another host? Please help.
Thank you, PK.
Thanks for Replying Akash. I did figured this out. The 10G lun mentioned in my post was actually a Basic lun and not a Thin Provisioned LUN, obviously UNMAP will say "unsupported". PK.
Hi Friends, I have an interesting issue where one of the VAAI primitive stays "unsupported" configuration: VMware ESXi, 5.1.0, 799733 Storage: Hitachi VSP                FC                T... See more...
Hi Friends, I have an interesting issue where one of the VAAI primitive stays "unsupported" configuration: VMware ESXi, 5.1.0, 799733 Storage: Hitachi VSP                FC                Two luns, 1) 10GB and 2) 1TB                Both are in same Host-Groups so same Host-mode options are applied to them. Here is what I see Only difference is the size - one lun is 10gb which is showing as everything supported while other one is 1TB and Delete Status says "unsupported" Your input is greatly appreciated. Thank you, PK.
Thanks again, can you please eloborate on what the runtime ( name ) is in esx? I am gogleing but not seeing any good info.
Thanks Matt for a quick response. I am not sure if there was a Lun on address 1 but could be. would rescan of vmbha fix this or reboot is necessary? I have 8 esx hosts in a cluster and rebooting ... See more...
Thanks Matt for a quick response. I am not sure if there was a Lun on address 1 but could be. would rescan of vmbha fix this or reboot is necessary? I have 8 esx hosts in a cluster and rebooting all of them is not something I want to go through.
After adding new LUN, here is what we see, Please see the attachded.It should match the LUN number L:144 to LUN ID which says 1 for example, why? Please help.