{"id":656,"date":"2019-01-29T21:09:13","date_gmt":"2019-01-29T20:09:13","guid":{"rendered":"https:\/\/virtualguru.cz\/?p=656"},"modified":"2019-01-29T21:09:13","modified_gmt":"2019-01-29T20:09:13","slug":"virtual-machine-disks-consolidation-is-needed","status":"publish","type":"post","link":"https:\/\/virtualguru.cz\/en\/2019\/01\/29\/virtual-machine-disks-consolidation-is-needed\/","title":{"rendered":"Virtual machine disks consolidation is needed"},"content":{"rendered":"

Virtual machine disks consolidation is needed, i takto V\u00e1s m\u016f\u017ee p\u0159iv\u00edtat vCenter v okn\u011b alarm\u016f po p\u0159ihl\u00e1\u0161en\u00ed. Na konkr\u00e9tn\u00edm VM, na z\u00e1lo\u017ece „Summary“, pak bude pod hlavn\u00edmi informacemi v oznamovac\u00ed oblasti sv\u00edtit:<\/p>\n

\"\"Jak\u00fd je d\u016fvod pot\u0159eby konsolidace?<\/h4>\n

K tomuto stavu doch\u00e1z\u00ed, pokud obsah *.vmsd (datab\u00e1ze snapshot\u016f) je rozd\u00edln\u00fd oproti re\u00e1ln\u00e9mu stavu. Typicky existuje delta soubor, ale v snapshot manageru nen\u00ed o aktivn\u00edm snapshotu \u017e\u00e1dn\u00fd z\u00e1znam.<\/p>\n

Jak k tomu do\u0161lo?<\/h4>\n

Nej\u010dast\u011bj\u0161\u00edm d\u016fvodem je z\u00e1lohov\u00e1n\u00ed pomoc\u00ed VM snapshot\u016f. M\u016f\u017ee doj\u00edt k n\u011bjak\u00e9 chyb\u011b nebo n\u011bkdy sta\u010d\u00ed v dob\u011b z\u00e1lohov\u00e1n\u00ed VM v nevhodnou dobu prov\u00e1d\u011bt \u00fadr\u017ebu hosta a m\u016f\u017ee doj\u00edt k tomuto stavu.<\/p>\n

Jak se prov\u00e1d\u00ed konsolidace?<\/h4>\n

Sta\u010d\u00ed pouze p\u0159es kontextovou nab\u00eddku nad dan\u00fdm VM v menu „Snapshots“ zvolit „Consolidate“ a probl\u00e9m je vy\u0159e\u0161en.<\/p>\n

Co kdy\u017e kon\u010d\u00ed chybou?<\/h4>\n

Pokud pokus o konsolidaci kon\u010d\u00ed chybou, je pot\u0159eba naj\u00edt d\u016fvod. P\u0159\u00edklad chyby m\u016f\u017ee vypadat takto:<\/p>\n

\"\"<\/a><\/p>\n

P\u0159\u00ed\u010dina je velice jednoduch\u00e1, jak je vid\u011bt v logu, samotn\u00fd disk m\u00e1 z\u00e1mek proti z\u00e1pisu. N\u011bjak\u00e1 komponenta jej dr\u017e\u00ed. Je tedy pot\u0159eba naj\u00edt vlastn\u00edka z\u00e1mku. A zde za\u010d\u00edn\u00e1 trochu detektivn\u00ed pr\u00e1ce.<\/p>\n

1.<\/strong> zjist\u00edme, na kter\u00e9m datastoru se VM nach\u00e1z\u00ed: nap\u0159\u00edklad pohledem do komponenty „VM Hardware“ na z\u00e1lo\u017ece „Summary“. U konkr\u00e9tn\u00edho disku je polo\u017eka „Location“, ta n\u00e1m \u0159\u00edk\u00e1, kde je disk um\u00edst\u011bn.
\n2.<\/strong> zapneme si na hostu SSH a p\u0159ipoj\u00edme se na n\u011bj.
\n3.<\/strong> p\u0159ejdeme na datastor a do slo\u017eky, ve kter\u00e9 m\u00e1me zamknut\u00e9 vm<\/p>\n

cd \/vmfs\/volumes\/datastore01\/LockedVM\/<\/pre>\n
4.<\/strong> ud\u011bl\u00e1me si v\u00fdpis soubor\u016f ve slo\u017ece:<\/p>\n
ls -l\r\n\r\ntotal 2022528\r\n-rw------- 1 root root 262656 Jan 17 08:11 LockedVM-000001-ctk.vmdk\r\n-rw------- 1 root root 37756928 Jan 17 08:11 LockedVM-000001-sesparse.vmdk\r\n-rw------- 1 root root 444 Jan 16 22:27 LockedVM-000001.vmdk\r\n-rw------- 1 root root 262656 Jan 17 08:11 LockedVM-000002-ctk.vmdk\r\n-rw------- 1 root root 37818368 Jan 17 08:11 LockedVM-000002-sesparse.vmdk\r\n-rw------- 1 root root 451 Jan 16 22:28 LockedVM-000002.vmdk\r\n-rw------- 1 root root 262656 Jan 17 08:11 LockedVM-000003-ctk.vmdk\r\n-rw------- 1 root root 37756928 Jan 17 08:11 LockedVM-000003-sesparse.vmdk\r\n-rw------- 1 root root 451 Jan 17 02:29 LockedVM-000003.vmdk\r\n-rw-r--r-- 1 root root 93 Jan 16 20:54 LockedVM-1905e506.hlog\r\n-rw------- 1 root root 536870912 Jan 10 15:03 LockedVM-53976208.vswp\r\n-rw------- 1 root root 262656 Jan 17 08:11 LockedVM-ctk.vmdk\r\n-rw------- 1 root root 4294967296 Jan 16 22:25 LockedVM-flat.vmdk\r\n-rw------- 1 root root 8684 Jan 17 09:05 LockedVM.nvram\r\n-rw------- 1 root root 622 Jan 16 20:54 LockedVM.vmdk\r\n-rw-r--r-- 1 root root 78 Jan 17 06:31 LockedVM.vmsd\r\n-rwxr-xr-x 1 root root 3744 Jan 17 06:31 LockedVM.vmx\r\n-rw------- 1 root root 0 Jan 16 20:54 LockedVM.vmx.lck\r\n-rwxr-xr-x 1 root root 3744 Jan 17 06:31 LockedVM.vmx~\r\n-rw-r--r-- 1 root root 656534 Jan 17 09:00 vmware.log<\/pre>\n
zde ji\u017e vid\u00edme, \u017ee na\u0161e posti\u017een\u00e9 VM m\u00e1 dokonce v\u00edce ne\u017e jeden snapshot, delta soubory LockedVM-00000x-sesparse.vmdk<\/p>\n
5.<\/strong> nyn\u00ed pou\u017eijeme n\u00e1stroj vmkfstools<\/code> nebo od ESXi 5.5 PO5 vmfsfilelockinfo<\/code> a zjist\u00edme MAC adresu nebo p\u0159\u00edmo vlastn\u00edka z\u00e1mku:<\/p>\n
vmkfstools -D .\/LockedVM-flat.vmdk\r\n\r\nLock [type 10c00001 offset 207536128 v 228, hb offset 4161536\r\ngen 15, mode 2, owner 00000000-00000000-0000-000000000000 mtime 122749\r\nnum 1 gblnum 0 gblgen 0 gblbrk 0]\r\nRO Owner[0] HB Offset 3997696 5c405611-f64ae6db-1385-52df370e6410\r\nAddr <4, 60, 46>, gen 85, links 1, type reg, flags 0x9, uid 0, gid 0, mode 600\r\nlen 4294967296, nb 1168 tbz 0, cow 0, newSinceEpoch 1168, zla 3, bs 1048576<\/pre>\n
RO Owner[0] HB Offset 3997696 5c405611-f64ae6db-1385-52df370e6410 = MAC adressa
\n<\/span><\/p>\n
nebo<\/p>\n
vmfsfilelockinfo -p .\/LockedVM-flat.vmdk\r\n\r\nvmfsfilelockinfo Version 2.0\r\nLooking for lock owners on \"LockedVM-flat.vmdk\"\r\n\"LockedVM-flat.vmdk\" is locked in Read-Only mode by host having mac address ['52:df:37:0e:64:10']\r\nTrying to use information from VMFS Heartbeat\r\n\r\nHost owning the lock on file is 192.168.3.7, lockMode : Read-Only<\/pre>\n
vmfsfilelockinfo<\/code> sd\u011bluje p\u0159\u00edmo IP hosta, je to pohodln\u011bj\u0161\u00ed n\u011b\u017e hledat, kter\u00e9mu hostovi MAC adresa pat\u0159\u00ed. Pokud byste ale p\u0159eci jen m\u011bli star\u0161\u00ed verzi a tento n\u00e1stroj V\u00e1m chyb\u011bl, tak MAC adresu najdete na konkr\u00e9tn\u00edm hostovi v z\u00e1lo\u017ece „Configure“ v polo\u017ece „Physical adapters“. T\u011bm, kte\u0159\u00ed maj\u00ed rad\u0161i CLI, velice dob\u0159e poslou\u017e\u00ed p\u0159\u00edkaz esxcli network nic list<\/code><\/p>\n
Pokud VM b\u011b\u017e\u00ed, je dobr\u00e9 jej vypnout, jinak m\u016f\u017eete vid\u011bt v\u00edce vlastn\u00edk\u016f z\u00e1mku a nemus\u00ed b\u00fdt jednoduch\u00e9 p\u0159ij\u00edt na toho spr\u00e1vn\u00e9ho:<\/p>\n
vmfsfilelockinfo -p .\/LockedVM-flat.vmdk\r\n\r\nvmfsfilelockinfo Version 2.0\r\nLooking for lock owners on \"LockedVM-flat.vmdk\"\r\n\"LockedVM-flat.vmdk\" is locked in Read-Only mode by host having mac address ['52:df:37:0e:64:10', '52:df:37:0e:24:60']\r\nTrying to use information from VMFS Heartbeat\r\n\r\nHost owning the lock on file is 192.168.3.7, lockMode : Read-Only\r\nHost owning the lock on file is 192.168.3.3, lockMode : Read-Only<\/pre>\n
6.<\/strong> pokud ji\u017e zn\u00e1me vlastn\u00edka z\u00e1mku, p\u0159ejdeme na dan\u00e9ho hosta a pou\u017eijeme p\u0159\u00edkaz:<\/p>\n
lsof | grep LockedVM\r\n\r\n74508 vmx FILE 73 \/vmfs\/volumes\/5b7f0cf0-c6e38c43-c676-52df370e6280\/Backup-Proxy\/LockedVM.vmdk-sesparse.REDO_oTqsSX\r\n74508 vmx FILE 74 \/vmfs\/volumes\/5c373e71-42669298-6824-52df370e6280\/LockedVM\/LockedVM-flat.vmdk<\/pre>\n
zde prvn\u00ed \u010d\u00edslo na \u0159\u00e1dku „74508“ \u0159\u00edk\u00e1 \u010d\u00edslo procesu, kter\u00fd soubor dr\u017e\u00ed.<\/p>\n
7.<\/strong> pokud je vin\u00edk z v\u00fdpisu jasn\u00fd, v na\u0161em p\u0159\u00edpad\u011b backup proxy, kter\u00e9 z\u016fstal disk p\u0159ipojen i po skon\u010den\u00ed z\u00e1lohov\u00e1n\u00ed, m\u016f\u017eeme v klidu ru\u010dn\u011b odmapovat. Pokud ale nevid\u00edme jasnou p\u0159\u00ed\u010dinu, tak pou\u017eijeme p\u0159\u00edkaz kill<\/code> a zastav\u00edme tak proces, kter\u00fd soubor dr\u017e\u00ed:<\/p>\n
kill -9 74508<\/pre>\n
Pokud jste tak neu\u010dinili ji\u017e d\u0159\u00edve, p\u0159ed samotn\u00fdm ukon\u010den\u00edm procesu je nutn\u00e9 m\u00edt VM ve vypnut\u00e9m stavu! V opa\u010dn\u00e9m p\u0159\u00edpad\u011b m\u016f\u017eeme p\u0159\u00edkazem kill<\/code> ukon\u010dit i b\u011bh samotn\u00e9ho VM.<\/p>\n
Ne v\u017edy na hostovi, kter\u00fd z\u00e1mek dr\u017e\u00ed, mus\u00ed b\u00fdt b\u011b\u017e\u00edc\u00ed proces, kter\u00fd evidentn\u011b z\u00e1mek dr\u017e\u00ed. V t\u011bchto p\u0159\u00edpadech m\u016f\u017ee pomoct p\u0159\u00edkaz:<\/p>\n
\/etc\/init.d\/hostd restart<\/pre>\n
8.<\/strong> kontrolu, \u017ee byl z\u00e1mek odstran\u011bn, provedeme takto:<\/p>\n
vmfsfilelockinfo -p .\/LockedVM-flat.vmdk\r\n\r\nvmfsfilelockinfo Version 2.0\r\nLooking for lock owners on \"LockedVM-flat.vmdk\"\r\n\"LockedVM-flat.vmdk\" is not locked by any ESX host and is Free<\/pre>\n
op\u011bt lze prov\u00e9st i pomoc\u00ed p\u0159\u00edkazu vmkfstools<\/code><\/p>\n
Podrobn\u011bj\u0161\u00ed informace o hled\u00e1n\u00ed majitele z\u00e1mku popisuj\u00ed KB10051<\/span><\/a> a KB2110152<\/span><\/a><\/p>\n
9.<\/strong> pokud jsme byli \u00fasp\u011b\u0161n\u00ed a z\u00e1mek je odstran\u011bn, tak ji\u017e sta\u010d\u00ed jen v GUI p\u0159es kontextovou nab\u00eddku nad dan\u00fdm VM v menu „Snapshots“ zvolit „Consolidate“ a probl\u00e9m je vy\u0159e\u0161en.<\/p>\n
 <\/p>","protected":false},"excerpt":{"rendered":"
Virtual machine disks consolidation is needed, i takto V\u00e1s m\u016f\u017ee p\u0159iv\u00edtat vCenter v okn\u011b alarm\u016f po p\u0159ihl\u00e1\u0161en\u00ed. Na konkr\u00e9tn\u00edm VM, na z\u00e1lo\u017ece „Summary“, pak bude…<\/p>\n
Continue ReadingVirtual machine disks consolidation is needed<\/span> <\/i><\/a><\/div>","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"iawp_total_views":244,"footnotes":""},"categories":[3],"tags":[19,9],"class_list":["post-656","post","type-post","status-publish","format-standard","hentry","category-vsphere","tag-vcsa","tag-vsphere","entry"],"_links":{"self":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/656","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/comments?post=656"}],"version-history":[{"count":21,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/656\/revisions"}],"predecessor-version":[{"id":680,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/656\/revisions\/680"}],"wp:attachment":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/media?parent=656"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/categories?post=656"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/tags?post=656"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}