VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Removing orphaned vswp objects from the Virtual SAN datastore As mentioned, in Virtual SAN 6.0, VMware has provided an RVC tool to clean up stranded vswp objects that are now inaccessible. This tool will purge all inaccessible vswp objects from the Virtual SAN datastore and allow a full data evacuation to take place. To ensure that the object is a vswp object and not some other object, the tool finds the active data components and reads the extended attributes that will tell us whether or not it is a vswp object. Note that if the inaccessible object only contains witness and there are no active data components, Virtual SAN cannot read the extended attributes, so it cannot determine if the stranded object is vswp object or some other object. However, assuming that the virtual machine was deployed with a NumberOfFailuresToTolerate=1 attribute, then there is 2 in 3 chance that the remaining component for the vswp object is an active data component and not the witness. In the case where the remaining component of the object is indeed the witness, the command will allow a user to force delete those witness-only objects. Caution: Extreme caution needs to exercise here because this command will also allow you to force delete non-vswp objects (which may cause a real data loss). If you are not completely sure that this is indeed a vswp object, please contact GSS for support with the upgrade. vsan.purge_inaccessible_vswp_objects > vsan.purge_inaccessible_vswp_objects -h usage: purge_inaccessible_vswp_objects [opts] cluster_or_host Search and delete inaccessible vswp objects on a virtual SAN cluster. cluster_or_host: Path to a ClusterComputeResource or HostSystem --force, -f: Force to delete the inaccessible vswp objects quietly (no interactive confirmations) --help, -h: Show this message If a vswp object goes inaccessible, this virtual machine will be unable to do any swapping. If the ESXi tries to swap this virtual machines pages while the vswp file is inaccessible, this may cause the virtual machines to crash. By deleting the inaccessible vswp object, things are not any worse for the virtual machine. However, it does remove all possibility of the object regaining accessibility in future time if this inaccessibility is due just a temporary issue on the cluster (e.g. due to network failure or planned maintenance). The command to purge inaccessible swap objects will not cause data loss by deleting the vswp object. The vswp object will be regenerated when the virtual machine is next powered on. V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 1 7 6
Diagnostics and Troubleshooting Reference Manual – Virtual SAN On-disk upgrade – out of resources to complete operation Because the upgrade procedure needs to evacuate disk groups before they can be upgraded to v2, you need to ensure that there are enough resources available in the cluster. If you do not have enough resources in the cluster, the upgrade will report the following: /ie-vcsa-03.ie.local/vsan-dc/computers> vsan.v2_ondisk_upgrade 0 +--------------------+-----------+-------------+----------------+----------------+ | Host | State | ESX version | v1 Disk-Groups | v2 Disk-Groups | +--------------------+-----------+-------------+----------------+----------------+ | cs-ie-h02.ie.local | connected | 6.0.0 | 1 | 0 | | cs-ie-h03.ie.local | connected | 6.0.0 | 1 | 0 | | cs-ie-h04.ie.local | connected | 6.0.0 | 1 | 0 | | cs-ie-h01.ie.local | connected | 6.0.0 | 1 | 0 | +--------------------+-----------+-------------+----------------+----------------+ 2014-12-10 14:42:29 +0000: Running precondition checks ... 2014-12-10 14:42:32 +0000: Passed precondition checks 2014-12-10 14:42:32 +0000: 2014-12-10 14:42:32 +0000: Target file system version: v2 2014-12-10 14:42:32 +0000: Disk mapping decommission mode: evacuateAllData 2014-12-10 14:42:38 +0000: Cluster is still in good state, proceeding ... 2014-12-10 14:42:41 +0000: Enabled v2 filesystem as default on host cs-ie-h02.ie.local 2014-12-10 14:42:41 +0000: Removing VSAN disk group on cs-ie-h02.ie.local: 2014-12-10 14:42:41 +0000: SSD: HP Serial Attached SCSI Disk (naa.600508b1001c64b76c8ceb56e816a89d) 2014-12-10 14:42:41 +0000: HDD: HP Serial Attached SCSI Disk (naa.600508b1001c19335174d82278dee603) 2014-12-10 14:42:41 +0000: HDD: HP Serial Attached SCSI Disk (naa.600508b1001ca36381622ca880f3aacd) 2014-12-10 14:42:41 +0000: HDD: HP Serial Attached SCSI Disk (naa.600508b1001cb2234d6ff4f7b1144f59) 2014-12-10 14:42:41 +0000: HDD: HP Serial Attached SCSI Disk (naa.600508b1001c0cc0ba2a3866cf8e28be) 2014-12-10 14:42:41 +0000: HDD: HP Serial Attached SCSI Disk (naa.600508b1001c07d525259e83da9541bf) 2014-12-10 14:42:41 +0000: HDD: HP Serial Attached SCSI Disk (naa.600508b1001c10548f5105fc60246b4a) RemoveDiskMapping cs-ie-h02.ie.local: SystemError: A general system error occurred: Failed to evacuate data for disk uuid 52271ef2-2c6e-c55e-2b2c-6fd76b0aa143 with error: Out of resources to complete the operation 2014-12-10 14:42:45 +0000: Failed to remove this disk group from VSAN 2014-12-10 14:42:45 +0000: A general system error occurred: Failed to evacuate data for disk uuid 52271ef2-2c6e-c55e-2b2c-6fd76b0aa143 with error: Out of resources to complete the operation 2014-12-10 14:42:48 +0000: Failed to remove disk group from VSAN, aborting. 2014-12-10 14:42:48 +0000: Upgrade tool stopped due to errors. /ie-vcsa-03.ie.local/vsan-dc/computers> Ensure there are enough resources available in the cluster to accommodate an upgrade. Note that fault domains also play a role here. If you have configured fault domains, ensure that there are enough resources in each domain to accommodate full evacuations of disk groups from other hosts/domains. V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 1 7 7
Page 1 and 2:
Diagnostics and Troubleshooting Gui
Page 3 and 4:
Diagnostics and Troubleshooting Ref
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126: Diagnostics and Troubleshooting Ref
Page 175: Diagnostics and Troubleshooting Ref
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295:
show all

VSAN-Troubleshooting-Reference-Manual

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?