1. shell 접속하여 datastore의 Device Name 을 확인
[root@localhost:/var/log] esxcli storage vmfs extent list
Volume Name VMFS UUID Extent Number Device Name Partition
-------------- ----------------------------------- ------------- ------------------------------------ ---------
datastore1 (2) 571fae59-fb80f017-85a3-141877583bc1 0 naa.61418770726049001eb262191de56b8f 3
datastore2 (2) 571fb6b8-199e5621-0d29-141877583bc1 0 naa.61418770726049001eb263af3615ebba 1
[root@localhost:/var/log]
2. 다음과 같이 검사 수행 (마지막 : 3은 partition 번호)
문제가 없으면 다음과 같은 결과
[root@localhost:/var/log] voma -m vmfs -f check -d /vmfs/devices/disks/naa.61418770726049001eb262191de56b8f:3
Checking if device is actively used by other hosts
Found 1 actively heartbeating hosts on device '/vmfs/devices/disks/naa.61418770726049001eb262191de56b8f:3'
1): MAC address 00:e0:ed:17:aa:64
[root@localhost:/var/log]
3. 문제가 많은 경우 Sample
/var/log # voma -m vmfs -f check -d /vmfs/devices/disks/naa.5000c5002a39eab0:1
Checking if device is actively used by other hosts
Running VMFS Checker version 0.9 in check mode
Initializing LVM metadata, Basic Checks will be done
Phase 1: Checking VMFS header and resource files
Detected file system (labeled:'datastore500G') with UUID:50daeab2-04d91ad4-9a32-001b21493454, Version 5:58
Phase 2: Checking VMFS heartbeat region
Phase 3: Checking all file descriptors.
ON-DISK ERROR: <FD c426 r45> : Invalid block count 327680 should be 0.
ON-DISK ERROR: <FD c426 r45> : Invalid TBZ block count 291 should be 0.
Found stale lock [type 10c00001 offset 183508992 v 154, hb offset 4022272
gen 255, mode 1, owner 54ee7010-42a4288d-6549-001b21493454 mtime 1526
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 183666688 v 240, hb offset 4022272
gen 255, mode 1, owner 54ee7010-42a4288d-6549-001b21493454 mtime 1449
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 183668736 v 239, hb offset 4022272
gen 255, mode 1, owner 54ee7010-42a4288d-6549-001b21493454 mtime 1452
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 183672832 v 239, hb offset 4022272
gen 231, mode 1, owner 54210476-1e763b75-372b-001b21493454 mtime 1539
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 183674880 v 242, hb offset 4022272
gen 255, mode 1, owner 54ee7010-42a4288d-6549-001b21493454 mtime 1510
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 183734272 v 297, hb offset 4022272
gen 255, mode 1, owner 54ee7010-42a4288d-6549-001b21493454 mtime 1477
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 183736320 v 298, hb offset 4022272
gen 255, mode 1, owner 54ee7010-42a4288d-6549-001b21493454 mtime 1501
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 183756800 v 318, hb offset 4022272
gen 327, mode 1, owner 561653f9-3ebe31fc-1eda-001b21493454 mtime 5857
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 183771136 v 327, hb offset 4022272
gen 341, mode 1, owner 5695ad51-61c516a8-dafa-001b21493454 mtime 907
num 0 gblnum 0 gblgen 0 gblbrk 0]
Phase 4: Checking pathname and connectivity.
Phase 5: Checking resource reference counts.
ON-DISK ERROR: PB inconsistency found: (2312,0) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (2312,1) allocated in bitmap, but never used
.....
ON-DISK ERROR: FB inconsistency found: (3989,79) allocated in bitmap, but never used
ON-DISK ERROR: FB inconsistency found: (3989,80) allocated in bitmap, but never used
ON-DISK ERROR: FB inconsistency found: (3989,81) allocated in bitmap, but never used
ON-DISK ERROR: FB inconsistency found: (3989,82) allocated in bitmap, but never used
ON-DISK ERROR: FB inconsistency found: (3989,83) allocated in bitmap, but never used
ON-DISK ERROR: FB inconsistency found: (3989,84) allocated in bitmap, but never used
ON-DISK ERROR: FB inconsistency found: (3989,85) allocated in bitmap, but never used
ON-DISK ERROR: FB inconsistency found: (3989,86) allocated in bitmap, but never used
Total Errors Found: 512502
/var/log #
4. vmfs 는 에러를 고칠 수 없다고 하는데... 방법이 없을까?
'Engineering > __00. Virtual OS' 카테고리의 다른 글
[vSphere] vSphere Web Client 한글 깨짐 (0) | 2018.02.22 |
---|---|
vSphere Web Client(Flash) crash issue (0) | 2017.10.27 |
[VMware] vCenter (0) | 2017.03.22 |
How to Increase the size of a Linux LVM by expanding the virtual machine disk (펌) (0) | 2016.04.26 |
[VMware_ESXi] Waiting for loading ipmi_si_drv ? (0) | 2015.09.10 |