{"id":2331,"date":"2015-07-10T13:59:42","date_gmt":"2015-07-10T11:59:42","guid":{"rendered":"http:\/\/vm.piszki.pl\/?p=2331"},"modified":"2015-07-10T14:17:33","modified_gmt":"2015-07-10T12:17:33","slug":"esxi-5-5-wyczerpanie-inodw-na-dysku-root-there-is-no-space-left-on-device","status":"publish","type":"post","link":"https:\/\/vm.piszki.pl\/?p=2331","title":{"rendered":"ESXi 5.5 &ndash; Wyczerpanie inod&oacute;w na dysku root (There is no space left on device)."},"content":{"rendered":"<p align=\"justify\">Dzisiaj spotka\u0142em si\u0119 z zaskakuj\u0105cym komunikatem, pojawi\u0142 si\u0119 on w \u015brodowisku produkcyjnym w trakcie pr\u00f3by umieszczenia nowej maszyny wirtualnej (w formacie ovf). Komunikat brzmia\u0142 tak: Failed to open \/var\/log\/journal for write (There is no space left on device). Zaskoczy\u0142o mnie to o tyle, \u017ce logi trzymamy na dysku innym ni\u017c root.<\/p>\n<p><a href=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal1.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"journal1\" src=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal1_thumb.png\" alt=\"journal1\" width=\"482\" height=\"183\" border=\"0\" \/><\/a><\/p>\n<p align=\"justify\">Szybkie sprawdzenie zaj\u0119to\u015bci dysk\u00f3w nie pokaza\u0142o niczego z\u0142ego:<\/p>\n<p><a href=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal2.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"journal2\" src=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal2_thumb.png\" alt=\"journal2\" width=\"452\" height=\"98\" border=\"0\" \/><\/a><\/p>\n<p align=\"justify\">Wniosek jest prosty, sko\u0144czy\u0142y si\u0119 inody, mo\u017cna to sprawdzi\u0107 bardzo szybko poleceniem &#8222;localcli system visorfs ramdisk list&#8221;:<\/p>\n<p><a href=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal3.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"journal3\" src=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal3_thumb.png\" alt=\"journal3\" width=\"448\" height=\"56\" border=\"0\" \/><\/a><\/p>\n<p align=\"justify\">Wyra\u017anie wida\u0107, \u017ce dysk root wyczerpa\u0142 dost\u0119pne w\u0119z\u0142y. Tego typu b\u0142\u0119dy s\u0105 ci\u0119\u017ckie w diagnostyce, i-w\u0119z\u0142y mog\u0105 zosta\u0107 zu\u017cyte przez du\u017ce ilo\u015bci ma\u0142ych plik\u00f3w lub np. przez plik logu z zerwanym deskryptorem (skasowali\u015bmy plik do kt\u00f3rego pisze system, nam si\u0119 wydaje \u017ce pliku nie ma a on ro\u015bnie). Na szcz\u0119\u015bcie uda\u0142o mi si\u0119 znale\u017a\u0107 <a href=\"http:\/\/kb.vmware.com\/selfservice\/microsites\/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=2037798\" target=\"_blank\">KB<\/a> kt\u00f3re dotyczy\u0142o mojego problemu. Ku mojemu nieustaj\u0105cemu zaskoczeniu, w katalogu \/var\/run\/sfcb znalaz\u0142em mn\u00f3stwo plik\u00f3w:<\/p>\n<p><a href=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal4.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"journal4\" src=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal4_thumb.png\" alt=\"journal4\" width=\"447\" height=\"60\" border=\"0\" \/><\/a><\/p>\n<p align=\"justify\">Procedura \u201cczyszczenia\u201d jest prosta, stopujemy watchdoga, usuwamy pliki i startujemy watchdoga. Sprawdzamy inody:<\/p>\n<p><a href=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal5.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"journal5\" src=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal5_thumb.png\" alt=\"journal5\" width=\"452\" height=\"53\" border=\"0\" \/><\/a><\/p>\n<p align=\"justify\">Liczba zaj\u0119tych w\u0119z\u0142\u00f3w spad\u0142a o po\u0142ow\u0119! Jak si\u0119 obroni\u0107 na przysz\u0142o\u015b\u0107 przed tym problemem? Mo\u017cemy zgodnie z KB skierowa\u0107 zapis tych plik\u00f3w do ramdysku:<\/p>\n<p>esxcli system visorfs ramdisk add &#8211;name sfcbtickets &#8211;min-size 0 &#8211;max-size 1024 &#8211;permissions 0755 &#8211;target \/var\/run\/sfcb<\/p>\n<p><a href=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal6.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"journal6\" src=\"https:\/\/vm.piszki.pl\/wp-content\/uploads\/2015\/07\/journal6_thumb.png\" alt=\"journal6\" width=\"449\" height=\"43\" border=\"0\" \/><\/a><\/p>\n<div style='text-align:left' class='yasr-auto-insert-visitor'><\/div>","protected":false},"excerpt":{"rendered":"<p>Dzisiaj spotka\u0142em si\u0119 z zaskakuj\u0105cym komunikatem, pojawi\u0142 si\u0119 on w \u015brodowisku produkcyjnym w trakcie pr\u00f3by umieszczenia nowej maszyny wirtualnej (w formacie ovf). Komunikat brzmia\u0142 tak: Failed to open \/var\/log\/journal for write (There is no space left on device). Zaskoczy\u0142o mnie &hellip; <a href=\"https:\/\/vm.piszki.pl\/?p=2331\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":1529,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"yasr_overall_rating":0,"yasr_post_is_review":"","yasr_auto_insert_disabled":"","yasr_review_type":"","footnotes":""},"categories":[48],"tags":[26,88],"class_list":["post-2331","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-drobne-poprawki","tag-esxi","tag-inode"],"yasr_visitor_votes":{"stars_attributes":{"read_only":false,"span_bottom":false},"number_of_votes":2,"sum_votes":9},"_links":{"self":[{"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=\/wp\/v2\/posts\/2331"}],"collection":[{"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2331"}],"version-history":[{"count":3,"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=\/wp\/v2\/posts\/2331\/revisions"}],"predecessor-version":[{"id":2334,"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=\/wp\/v2\/posts\/2331\/revisions\/2334"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=\/wp\/v2\/media\/1529"}],"wp:attachment":[{"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vm.piszki.pl\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}