VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN On-disk format post upgrade check: vsan.disks_stats Finally, the v2 on-disk format can be checked once again with vsan.disks_stats. The version of the on-disk format is shown in the Status Health column on the right hand side: > vsan.disks_stats computers/vsan/ +--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+ | | | | Num | Capacity | | | Status | | DisplayName | Host | isSSD | Comp | Total | Used | Reserved | Health | +--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+ | naa.600508b1001c61cedd42b0c3fbf55132 | cs-ie-h01.ie.local | SSD | 0 | 186.27 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001c3ea7838c0436dbe6d7a2 | cs-ie-h01.ie.local | MD | 0 | 136.69 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001c388c92e817e43fcd5237 | cs-ie-h01.ie.local | MD | 0 | 136.69 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001ccd5d506e7ed19c40a64c | cs-ie-h01.ie.local | MD | 0 | 136.69 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001c2ee9a6446e708105054b | cs-ie-h01.ie.local | MD | 0 | 136.69 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001c16be6e256767284eaf88 | cs-ie-h01.ie.local | MD | 0 | 136.69 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001c79748e8465571b6f4a46 | cs-ie-h01.ie.local | MD | 0 | 136.69 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001c64816271482a56a48c3c | cs-ie-h01.ie.local | MD | 0 | 136.69 GB | 0 % | 0 % | OK (v2) | +--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+ | naa.600508b1001c64b76c8ceb56e816a89d | cs-ie-h02.ie.local | SSD | 0 | 186.27 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001c0cc0ba2a3866cf8e28be | cs-ie-h02.ie.local | MD | 17 | 136.69 GB | 10 % | 10 % | OK (v2) | | naa.600508b1001cb2234d6ff4f7b1144f59 | cs-ie-h02.ie.local | MD | 15 | 136.69 GB | 4 % | 4 % | OK (v2) | | naa.600508b1001c19335174d82278dee603 | cs-ie-h02.ie.local | MD | 17 | 136.69 GB | 4 % | 4 % | OK (v2) | | naa.600508b1001c10548f5105fc60246b4a | cs-ie-h02.ie.local | MD | 17 | 136.69 GB | 3 % | 3 % | OK (v2) | | naa.600508b1001ca36381622ca880f3aacd | cs-ie-h02.ie.local | MD | 14 | 136.69 GB | 3 % | 3 % | OK (v2) | | naa.600508b1001c07d525259e83da9541bf | cs-ie-h02.ie.local | MD | 17 | 136.69 GB | 2 % | 2 % | OK (v2) | +--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+ | naa.600508b1001c9c8b5f6f0d7a2be44433 | cs-ie-h03.ie.local | SSD | 0 | 186.27 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001c2b7a3d39534ac6beb92d | cs-ie-h03.ie.local | MD | 19 | 136.69 GB | 3 % | 3 % | OK (v2) | | naa.600508b1001ceefc4213ceb9b51c4be4 | cs-ie-h03.ie.local | MD | 15 | 136.69 GB | 3 % | 3 % | OK (v2) | | naa.600508b1001cd259ab7ef213c87eaad7 | cs-ie-h03.ie.local | MD | 15 | 136.69 GB | 4 % | 4 % | OK (v2) | | naa.600508b1001cb11f3292fe743a0fd2e7 | cs-ie-h03.ie.local | MD | 13 | 136.69 GB | 3 % | 3 % | OK (v2) | | naa.600508b1001c9b93053e6dc3ea9bf3ef | cs-ie-h03.ie.local | MD | 17 | 136.69 GB | 8 % | 8 % | OK (v2) | | naa.600508b1001c1a7f310269ccd51a4e83 | cs-ie-h03.ie.local | MD | 18 | 136.69 GB | 18 % | 18 % | OK (v2) | +--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+ | naa.600508b1001cf639237aaffff152af66 | cs-ie-h04.ie.local | SSD | 0 | 186.27 GB | 0 % | 0 % | OK (v2) | | naa.600508b1001cadff5d80ba7665b8f09a | cs-ie-h04.ie.local | MD | 18 | 136.69 GB | 16 % | 11 % | OK (v2) | | naa.600508b1001c51f3a696fe0bbbcb5096 | cs-ie-h04.ie.local | MD | 20 | 136.69 GB | 8 % | 2 % | OK (v2) | | naa.600508b1001c4b820b4d80f9f8acfa95 | cs-ie-h04.ie.local | MD | 14 | 136.69 GB | 21 % | 1 % | OK (v2) | | naa.600508b1001c6a664d5d576299cec941 | cs-ie-h04.ie.local | MD | 13 | 136.69 GB | 5 % | 1 % | OK (v2) | | naa.600508b1001c258181f0a088f6e40dab | cs-ie-h04.ie.local | MD | 16 | 136.69 GB | 7 % | 2 % | OK (v2) | | naa.600508b1001c846c000c3d9114ed71b3 | cs-ie-h04.ie.local | MD | 16 | 136.69 GB | 6 % | 1 % | OK (v2) | +--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+ 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 4
Diagnostics and Troubleshooting Reference Manual – Virtual SAN On-disk upgrade concerns – inaccessible swap objects During an upgrade process, if there are any inaccessible vswp (swap) objects on a disk, this may prevent a full data migration from a host in the Virtual SAN cluster. This will prevent an upgrade from v1 to v2 on-disk format. > vsan.v2_ondisk_upgrade ie-vcsa-03.ie.local/vsan-dc/computers/vsan/ +--------------------+-----------+-------------+----------------+----------------+ | 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:19:00 +0000: Running precondition checks ... 2014-12-10 14:19:01 +0000: Detected inaccessible objects in VSAN. Upgrade has been 2014-12-10 14:19:01 +0000: halted. Please fix or remove them and try again. Following 2014-12-10 14:19:01 +0000: inaccessible objects were detected: 2014-12-10 14:19:01 +0000: 34723e54-7840-c72e-42a5-0010185def78\n4a743e54-f452-4435-1d15- 001f29595f9f\n3a743e54-a8c2-d13d-6d0c-001f29595f9f\n6e713e54-4819-af51-edb5- 0010185def78\n2d6d3e54-848f-3256-b7d0-001b21168828\nf0703e54-4404-c85b-0742- 001f29595f9f\n76723e54-74a3-0075-c1a9-001b21168828\ne4c33b54-1824-537c-472e- 0010185def78\nef713e54-186d-d77c-bf27-001b21168828\n77703e54-0420-3a81-dc1a- 001f29595f9f\n30af3e54-24fe-4699-f300-001b21168828\n58723e54-047e-86a0-4803- 001b21168828\n85713e54-dcbe-fea6-8205-001b21168828\nc2733e54-ac02-78ca-f0ce- 001f29595f9f\n94713e54-08e1-18d3-ffd7-001b21168828\nf0723e54-18d2-79f5-be44- 001b21168828\n3b713e54-9851-31f6-2679-001f29595f9f\nfd743e54-1863-c6fb-1845- 001f29595f9f\n94733e54-e81c-c3fe-8bfc-001b21168828 > The vswp file (virtual machine swap) is used for swapping memory to disk for VMs that have memory resource issues. The ESXi host handles this. In Virtual SAN, a vswp file is stored as a separate Virtual SAN object. Due to a known issue in vSphere 5.5, it is possible for Virtual SAN to have done incomplete deletions of vswp objects. For example, if one of the hosts that contained a component of the object was (temporarily) down at the time of deletion. In such cases, the majority of components of the vswp object were deleted/removed, but a minority of components was left behind on the hosts that were down. When the host or hosts are brought back online, the minority of the components on those hosts, which were not deleted, resurfaces. These now present themselves as an inaccessible object because a minority of components can never gain quorum. Such objects waste space and cause issues for any operations involving full data migrations, such as maintenance mode, from these hosts or disks. This means that administrators will be unable to completely evacuate all of the components from the disks on a certain host, which will mean you will not be able to upgrade the on-disk format from v1 to v2. Fortunately, RVC has the tools available to clean up the stranded objects and complete the full data migration from the disks that will allow the on-disk upgrade to continue. 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 5
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: Diagnostics and Troubleshooting Ref
Page 173: Diagnostics and Troubleshooting Ref
Page 225 and 226:
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

Create successful ePaper yourself

Delete template?

Save as template?