{"id":5788,"date":"2026-09-29T11:44:04","date_gmt":"2026-09-29T08:44:04","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/?p=5788"},"modified":"2026-09-29T06:17:32","modified_gmt":"2026-09-29T03:17:32","slug":"bulut-sunucuda-disk-buyutme-dosya-sistemi-ayari","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/bulut-sunucuda-disk-buyutme-dosya-sistemi-ayari\/","title":{"rendered":"Bulut Sunucuda Disk B\u00fcy\u00fctme ve Dosya Sistemi Ayar\u0131"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div class=\"aiw-summary\">\n<p class=\"aiw-box-title\">H\u0131zl\u0131 \u00f6zet<\/p>\n<p>Bulut panelinde disk hacmini b\u00fcy\u00fctmek, Linux i\u00e7indeki partition ve dosya sistemini her zaman otomatik b\u00fcy\u00fctmez. \u00d6nce i\u015fletim sisteminin yeni alan\u0131 g\u00f6r\u00fcp g\u00f6rmedi\u011fini belirleyin; ard\u0131ndan kulland\u0131\u011f\u0131n\u0131z yerle\u015fime g\u00f6re partition, LVM ve dosya sistemi katmanlar\u0131n\u0131 s\u0131rayla geni\u015fletin.<\/p>\n<ul>\n<li>\u0130\u015fleme ba\u015flamadan \u00f6nce g\u00fcncel yedek veya kullan\u0131labilir bir anl\u0131k g\u00f6r\u00fcnt\u00fc haz\u0131rlay\u0131n.<\/li>\n<li><code>lsblk<\/code>, <code>findmnt<\/code> ve <code>df -hT<\/code> \u00e7\u0131kt\u0131lar\u0131yla disk, partition, mant\u0131ksal birim ve dosya sistemi ili\u015fkisini do\u011frulay\u0131n.<\/li>\n<li>LVM kullan\u0131yorsan\u0131z genellikle <code>pvresize<\/code>, <code>lvextend<\/code> ve dosya sistemi b\u00fcy\u00fctme ad\u0131mlar\u0131 gerekir.<\/li>\n<li>ext4 \u00e7evrim i\u00e7i b\u00fcy\u00fct\u00fclebilir; XFS i\u00e7in b\u00fcy\u00fctme i\u015flemi ba\u011fl\u0131 dosya sistemi \u00fczerinde <code>xfs_growfs<\/code> ile yap\u0131l\u0131r. XFS k\u00fc\u00e7\u00fclt\u00fclemez.<\/li>\n<li>Her katmandan sonra kapasiteyi yeniden \u00f6l\u00e7\u00fcn; paneldeki toplam kapasite ile uygulaman\u0131n kullan\u0131labilir alan\u0131n\u0131 ayn\u0131 kabul etmeyin.<\/li>\n<\/ul>\n<\/div>\n<p>Bulut sunucunuzda panel \u00fczerinden disk boyutunu art\u0131rd\u0131n\u0131z, ancak <code>df -h<\/code> h\u00e2l\u00e2 eski kapasiteyi g\u00f6steriyor olabilir. Bu durum \u00e7o\u011funlukla i\u015flemin ba\u015far\u0131s\u0131z oldu\u011funu de\u011fil, depolama katmanlar\u0131n\u0131n yaln\u0131zca bir b\u00f6l\u00fcm\u00fcn\u00fcn b\u00fcy\u00fcd\u00fc\u011f\u00fcn\u00fc g\u00f6sterir.<\/p>\n<p>Bir sanal diskin kapasitesi genellikle \u015fu katmanlardan olu\u015fur: bulut sa\u011flay\u0131c\u0131n\u0131n sundu\u011fu sanal disk, i\u015fletim sistemi i\u00e7indeki partition, varsa LVM fiziksel hacmi (PV) ve mant\u0131ksal birimi (LV), en \u00fcstte de ext4 veya XFS gibi dosya sistemi. Bulut panelindeki de\u011fi\u015fiklik ilk katman\u0131 b\u00fcy\u00fct\u00fcr. Di\u011fer katmanlar i\u00e7in i\u015fletim sistemi i\u00e7inde ayr\u0131ca i\u015flem yapman\u0131z gerekebilir.<\/p>\n<p>Bu rehberde bulut sunucuda disk b\u00fcy\u00fctme i\u015flemini LVM kullanan, do\u011frudan partition \u00fczerinde \u00e7al\u0131\u015fan ext4 ve XFS senaryolar\u0131yla ele alaca\u011f\u0131z. Komutlarda \u00f6rnek cihaz adlar\u0131 kullan\u0131l\u0131r; kendi sunucunuzdaki \u00e7\u0131kt\u0131y\u0131 do\u011frulamadan cihaz ad\u0131n\u0131 kopyalamay\u0131n.<\/p>\n<div id=\"toc_container\" role=\"navigation\" aria-label=\"Table of Contents\" data-nosnippet class=\"toc_transparent no_bullets toc_numbered toc_title_center\"><p class=\"toc_title\">\u0130\u00e7indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Disk_buyudugu_halde_neden_alan_artmaz\"><span class=\"toc_number toc_depth_1\">1.<\/span> Disk b\u00fcy\u00fcd\u00fc\u011f\u00fc h\u00e2lde neden alan artmaz?<\/a><\/li><li><a href=\"#Islem_oncesi_yerlesimi_ve_onkosullari_dogrulayin\"><span class=\"toc_number toc_depth_1\">2.<\/span> \u0130\u015flem \u00f6ncesi yerle\u015fimi ve \u00f6nko\u015fullar\u0131 do\u011frulay\u0131n<\/a><\/li><li><a href=\"#LVM_kullanan_sunucuda_kapasiteyi_genisletme\"><span class=\"toc_number toc_depth_1\">3.<\/span> LVM kullanan sunucuda kapasiteyi geni\u015fletme<\/a><ul><li><a href=\"#Once_fiziksel_partition8217i_buyutun\"><span class=\"toc_number toc_depth_2\">3.1.<\/span> \u00d6nce fiziksel partition&#8217;\u0131 b\u00fcy\u00fct\u00fcn<\/a><\/li><li><a href=\"#PV_ve_LV_katmanlarini_genisletin\"><span class=\"toc_number toc_depth_2\">3.2.<\/span> PV ve LV katmanlar\u0131n\u0131 geni\u015fletin<\/a><\/li><li><a href=\"#Dosya_sistemini_buyutun_ve_dogrulayin\"><span class=\"toc_number toc_depth_2\">3.3.<\/span> Dosya sistemini b\u00fcy\u00fct\u00fcn ve do\u011frulay\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#LVM_olmayan_ext4_partition8217ini_buyutme\"><span class=\"toc_number toc_depth_1\">4.<\/span> LVM olmayan ext4 partition&#8217;\u0131n\u0131 b\u00fcy\u00fctme<\/a><\/li><li><a href=\"#XFS_kullanan_sunucuda_dogru_katmani_buyutun\"><span class=\"toc_number toc_depth_1\">5.<\/span> XFS kullanan sunucuda do\u011fru katman\u0131 b\u00fcy\u00fct\u00fcn<\/a><\/li><li><a href=\"#Islem_sonrasi_dogrulama_ve_geri_donus_plani\"><span class=\"toc_number toc_depth_1\">6.<\/span> \u0130\u015flem sonras\u0131 do\u011frulama ve geri d\u00f6n\u00fc\u015f plan\u0131<\/a><\/li><li><a href=\"#Sik_Sorulan_Sorular\"><span class=\"toc_number toc_depth_1\">7.<\/span> S\u0131k Sorulan Sorular<\/a><ul><li><a href=\"#Sunucuyu_yeniden_baslatmadan_disk_buyutulebilir_mi\"><span class=\"toc_number toc_depth_2\">7.1.<\/span> Sunucuyu yeniden ba\u015flatmadan disk b\u00fcy\u00fct\u00fclebilir mi?<\/a><\/li><li><a href=\"#Panelde_disk_boyutu_artti_ama_du_neden_degismedi\"><span class=\"toc_number toc_depth_2\">7.2.<\/span> Panelde disk boyutu artt\u0131 ama du neden de\u011fi\u015fmedi?<\/a><\/li><li><a href=\"#Bos_alanin_tamamini_kok_LV8217ye_vermeli_miyim\"><span class=\"toc_number toc_depth_2\">7.3.<\/span> Bo\u015f alan\u0131n tamam\u0131n\u0131 k\u00f6k LV&#8217;ye vermeli miyim?<\/a><\/li><li><a href=\"#Dosya_sistemi_buyutuldukten_sonra_uygulamayi_yeniden_baslatmak_gerekir_mi\"><span class=\"toc_number toc_depth_2\">7.4.<\/span> Dosya sistemi b\u00fcy\u00fct\u00fcld\u00fckten sonra uygulamay\u0131 yeniden ba\u015flatmak gerekir mi?<\/a><\/li><\/ul><\/li><li><a href=\"#Uygulanabilir_kontrol_listesi\"><span class=\"toc_number toc_depth_1\">8.<\/span> Uygulanabilir kontrol listesi<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Disk_buyudugu_halde_neden_alan_artmaz\">Disk b\u00fcy\u00fcd\u00fc\u011f\u00fc h\u00e2lde neden alan artmaz?<\/span><\/h2>\n<p>\u0130lk belirti, panelde yeni disk boyutunu g\u00f6rmenize ra\u011fmen <code>df -h<\/code> \u00e7\u0131kt\u0131s\u0131nda k\u00f6k dosya sisteminin eski boyutunu g\u00f6stermesidir. Bunun nedeni dosya sisteminin kendisini otomatik olarak b\u00fcy\u00fctmemi\u015f olmas\u0131 olabilir. Ba\u015fka bir ihtimalde \u00e7ekirdek yeni disk boyutunu hen\u00fcz alg\u0131lamam\u0131\u015f veya partition tablosu kullan\u0131labilir bo\u015f alan\u0131 kapsam\u0131yordur.<\/p>\n<p>Dosya sistemi, \u00fczerinde bulundu\u011fu blok cihaz\u0131n tamam\u0131n\u0131 kendili\u011finden kullanmaz. \u00d6rne\u011fin <code>\/dev\/sda<\/code> diski 100 GB&#8217;tan 150 GB&#8217;a \u00e7\u0131kar\u0131lm\u0131\u015f, ancak <code>\/dev\/sda3<\/code> partition&#8217;\u0131 100 GB&#8217;ta b\u0131rak\u0131lm\u0131\u015f olabilir. Bu durumda dosya sistemi 50 GB&#8217;l\u0131k yeni alan\u0131 g\u00f6remez.<\/p>\n<p>LVM kullan\u0131lan bir kurulumda zincir daha uzundur. Yeni alan \u00f6nce partition&#8217;a, sonra fiziksel hacme (PV), ard\u0131ndan hacim grubuna (VG) ve mant\u0131ksal birime (LV) aktar\u0131l\u0131r. En son dosya sistemi b\u00fcy\u00fct\u00fcl\u00fcr. Bir katman\u0131 atlamak, alan\u0131n bir sonraki katmanda beklemesine yol a\u00e7ar.<\/p>\n<div class=\"aiw-note aiw-note-warning\">\n<p class=\"aiw-box-title\">Dikkat<\/p>\n<p>Partition ve LVM komutlar\u0131 yanl\u0131\u015f cihaza uyguland\u0131\u011f\u0131nda veri kayb\u0131na neden olabilir. \u00dcretim sunucusunda i\u015flem \u00f6ncesi yedek, anl\u0131k g\u00f6r\u00fcnt\u00fc veya sa\u011flay\u0131c\u0131n\u0131z\u0131n destekledi\u011fi geri d\u00f6n\u00fc\u015f se\u00e7ene\u011fini haz\u0131rlay\u0131n. Geri y\u00fckleme ya da anl\u0131k g\u00f6r\u00fcnt\u00fcye d\u00f6nme ad\u0131mlar\u0131n\u0131n ger\u00e7ekten uygulanabilir oldu\u011funu \u00f6nceden kontrol edin.<\/p>\n<\/div>\n<h2><span id=\"Islem_oncesi_yerlesimi_ve_onkosullari_dogrulayin\">\u0130\u015flem \u00f6ncesi yerle\u015fimi ve \u00f6nko\u015fullar\u0131 do\u011frulay\u0131n<\/span><\/h2>\n<p>SSH oturumunuzu a\u00e7\u0131k tutun ve m\u00fcmk\u00fcnse ayr\u0131 bir y\u00f6netim oturumu haz\u0131rlay\u0131n. K\u00f6k diskte alan yetersizse paket kurma veya g\u00fcnl\u00fck yazma i\u015flemleri de sorun \u00e7\u0131karabilir. Kritik yazma i\u015flemlerini azalt\u0131n ve veri de\u011fi\u015ftiren ad\u0131mlar\u0131 planl\u0131 bir bak\u0131m aral\u0131\u011f\u0131na al\u0131n.<\/p>\n<p>A\u015fa\u011f\u0131daki komutlar yaln\u0131zca okuma yapar. Ama\u00e7, yeni kapasitenin diskte g\u00f6r\u00fcn\u00fcp g\u00f6r\u00fcnmedi\u011fini, hangi partition&#8217;\u0131n ba\u011fl\u0131 oldu\u011funu ve dosya sistemi t\u00fcr\u00fcn\u00fc bulmakt\u0131r. <code>pvs<\/code>, <code>vgs<\/code> ve <code>lvs<\/code> i\u00e7in LVM ara\u00e7lar\u0131n\u0131n kurulu olmas\u0131 gerekir.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS\nfindmnt -no SOURCE,FSTYPE,TARGET \/\ndf -hT\nsudo pvs\nsudo vgs\nsudo lvs<\/code><\/pre>\n<p>LVM bulunmad\u0131\u011f\u0131nda <code>pvs<\/code>, <code>vgs<\/code> ve <code>lvs<\/code> hata veya bo\u015f \u00e7\u0131kt\u0131 verebilir; bu tek ba\u015f\u0131na bir sorun de\u011fildir. <code>findmnt<\/code> \u00e7\u0131kt\u0131s\u0131nda k\u00f6k dosya sisteminin kayna\u011f\u0131 do\u011frudan <code>\/dev\/sda3<\/code> gibi bir partition ise do\u011frudan partition senaryosuna, <code>\/dev\/mapper\/...<\/code> bi\u00e7imindeyse genellikle LVM senaryosuna bakars\u0131n\u0131z.<\/p>\n<p>Paneldeki kapasite art\u0131\u015f\u0131ndan sonra <code>lsblk<\/code> ana diski h\u00e2l\u00e2 eski boyutta g\u00f6steriyorsa dosya sistemi komutlar\u0131na ge\u00e7meyin. Sa\u011flay\u0131c\u0131n\u0131n panelindeki i\u015fin tamamland\u0131\u011f\u0131n\u0131, sunucunun yeniden ba\u015flat\u0131lmas\u0131n\u0131n gerekip gerekmedi\u011fini ve sanal diskin \u00e7evrim i\u00e7i b\u00fcy\u00fctmeyi destekleyip desteklemedi\u011fini kontrol edin. Gerekirse planl\u0131 bir yeniden ba\u015flatma yap\u0131n; bunun uygulaman\u0131z \u00fczerindeki etkisini \u00f6nceden de\u011ferlendirin.<\/p>\n<p>Yeni boyut diskte g\u00f6r\u00fcn\u00fcr, fakat son partition&#8217;\u0131n boyutu eski kal\u0131rsa ve partition&#8217;\u0131n hemen sonras\u0131nda ayr\u0131lmam\u0131\u015f alan varsa yaln\u0131zca bu partition&#8217;\u0131n geni\u015fletilmesi gerekir. Partition tablosunu de\u011fi\u015ftirmeden \u00f6nce <code>lsblk<\/code> ve <code>findmnt<\/code> \u00e7\u0131kt\u0131lar\u0131n\u0131 kaydedin. Son partition de\u011filse veya arada ba\u015fka partition bulunuyorsa <code>growpart<\/code> bekledi\u011finiz sonucu vermeyebilir.<\/p>\n<div class=\"aiw-note aiw-note-example\">\n<p class=\"aiw-box-title\">\u00d6rnek senaryo<\/p>\n<p>Varsayal\u0131m ki panelde sanal disk 100 GB&#8217;tan 200 GB&#8217;a \u00e7\u0131kar\u0131lm\u0131\u015f, <code>lsblk<\/code> \u00e7\u0131kt\u0131s\u0131nda <code>\/dev\/sda<\/code> 200 GB g\u00f6r\u00fcnm\u00fc\u015f, fakat k\u00f6k partition olan <code>\/dev\/sda3<\/code> h\u00e2l\u00e2 100 GB kalm\u0131\u015f olsun. Bu varsay\u0131mda \u00f6nce partition&#8217;\u0131n sonundaki ayr\u0131lmam\u0131\u015f alan do\u011frulan\u0131r ve partition b\u00fcy\u00fct\u00fcl\u00fcr; ext4 veya XFS b\u00fcy\u00fctme komutu ise partition boyutu kontrol edildikten sonra \u00e7al\u0131\u015ft\u0131r\u0131l\u0131r.<\/p>\n<\/div>\n<h2><span id=\"LVM_kullanan_sunucuda_kapasiteyi_genisletme\">LVM kullanan sunucuda kapasiteyi geni\u015fletme<\/span><\/h2>\n<p>LVM, diskin kapasitesini mant\u0131ksal birimlere ay\u0131rmay\u0131 kolayla\u015ft\u0131r\u0131r. Bunun kar\u015f\u0131l\u0131\u011f\u0131nda disk ile dosya sistemi aras\u0131nda daha fazla katman vard\u0131r. \u00d6rnek olarak k\u00f6k dosya sisteminin <code>\/dev\/mapper\/ubuntu--vg-ubuntu--lv<\/code> \u00fczerinde, fiziksel LVM partition&#8217;\u0131n\u0131n da <code>\/dev\/sda3<\/code> \u00fczerinde oldu\u011funu varsayal\u0131m. Kendi \u00e7\u0131kt\u0131n\u0131z farkl\u0131 olabilir.<\/p>\n<h3><span id=\"Once_fiziksel_partition8217i_buyutun\">\u00d6nce fiziksel partition&#8217;\u0131 b\u00fcy\u00fct\u00fcn<\/span><\/h3>\n<p><code>lsblk<\/code> ana diskin b\u00fcy\u00fcd\u00fc\u011f\u00fcn\u00fc, ancak LVM partition&#8217;\u0131n\u0131n eski kald\u0131\u011f\u0131n\u0131 g\u00f6steriyorsa partition&#8217;\u0131 geni\u015fletin. Debian ve Ubuntu tabanl\u0131 sistemlerde <code>growpart<\/code> komutu bu i\u015f i\u00e7in kullan\u0131labilir. Komutun mevcut olup olmad\u0131\u011f\u0131n\u0131 kontrol edin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">command -v growpart<\/code><\/pre>\n<p>Komut bulunam\u0131yorsa da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n paket y\u00f6neticisiyle, \u00f6nko\u015fullar\u0131 ve bak\u0131m prosed\u00fcr\u00fcn\u00fc dikkate alarak <code>cloud-guest-utils<\/code> veya e\u015fde\u011fer paketi kurun. Paket ad\u0131 da\u011f\u0131t\u0131ma g\u00f6re de\u011fi\u015febilir. Paket kurulumundan \u00f6nce yedekleme ve geri d\u00f6n\u00fc\u015f plan\u0131n\u0131z\u0131n haz\u0131r oldu\u011fundan emin olun. Ard\u0131ndan yaln\u0131zca \u00f6rnekteki disk ve partition numaras\u0131n\u0131 kendi <code>lsblk<\/code> \u00e7\u0131kt\u0131n\u0131zla do\u011frulad\u0131ktan sonra \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo growpart \/dev\/sda 3\nlsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS<\/code><\/pre>\n<p>Burada <code>\/dev\/sda<\/code> disk, <code>3<\/code> ise partition numaras\u0131d\u0131r. Partition boyutu beklenen de\u011fere ula\u015fmad\u0131ysa sonraki katmana ge\u00e7meyin. GPT veya \u00f6zel partition d\u00fczenlerinde kullan\u0131lan ara\u00e7 ve i\u015flem s\u0131ras\u0131 farkl\u0131la\u015fabilir; belirsizlik varsa da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n ve sunucu sa\u011flay\u0131c\u0131n\u0131z\u0131n dok\u00fcmantasyonunu izleyin.<\/p>\n<h3><span id=\"PV_ve_LV_katmanlarini_genisletin\">PV ve LV katmanlar\u0131n\u0131 geni\u015fletin<\/span><\/h3>\n<p>Partition b\u00fcy\u00fcd\u00fckten sonra LVM fiziksel hacmi eski boyutta kalabilir. <code>pvs<\/code> ve <code>pvdisplay<\/code> ile bo\u015f alan\u0131n LVM taraf\u0131ndan g\u00f6r\u00fcl\u00fcp g\u00f6r\u00fclmedi\u011fini kontrol edin. \u00d6rnek cihaz LVM fiziksel hacmi olan <code>\/dev\/sda3<\/code> ise:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo pvresize \/dev\/sda3\nsudo pvs\nsudo vgs<\/code><\/pre>\n<p><code>vgs<\/code> \u00e7\u0131kt\u0131s\u0131ndaki bo\u015f alan, hacim grubunda kullan\u0131labilir alan bulundu\u011funu g\u00f6sterir. Bu alan\u0131 hangi mant\u0131ksal birime aktaraca\u011f\u0131n\u0131z\u0131 belirlemeden <code>lvextend<\/code> \u00e7al\u0131\u015ft\u0131rmay\u0131n. Birden fazla LV varsa t\u00fcm bo\u015f alan\u0131 yanl\u0131\u015f birime vermek uygulaman\u0131n beklenmedik \u015fekilde davranmas\u0131na neden olabilir.<\/p>\n<p>Belirli bir boyut eklemek istiyorsan\u0131z \u00f6rne\u011fin 40 GB kullanabilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo lvextend -L +40G \/dev\/mapper\/ubuntu--vg-ubuntu--lv<\/code><\/pre>\n<p>Hacim grubundaki bo\u015f alan\u0131n tamam\u0131n\u0131 bu LV&#8217;ye vermek istiyorsan\u0131z:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo lvextend -l +100%FREE \/dev\/mapper\/ubuntu--vg-ubuntu--lv<\/code><\/pre>\n<p>Bu komutlar mant\u0131ksal birimi b\u00fcy\u00fct\u00fcr; dosya sistemi her yap\u0131land\u0131rmada otomatik b\u00fcy\u00fcmeyebilir. Baz\u0131 sistemlerde <code>lvextend -r<\/code> dosya sistemi b\u00fcy\u00fctmesini de \u00e7a\u011f\u0131rabilir, ancak \u00fcretim ortam\u0131nda katmanlar\u0131 ayr\u0131 ayr\u0131 g\u00f6rmek ve her ad\u0131m\u0131n sonucunu do\u011frulamak daha kontroll\u00fc bir yakla\u015f\u0131md\u0131r.<\/p>\n<h3><span id=\"Dosya_sistemini_buyutun_ve_dogrulayin\">Dosya sistemini b\u00fcy\u00fct\u00fcn ve do\u011frulay\u0131n<\/span><\/h3>\n<p>Dosya sistemi ext4 ise ba\u011fl\u0131 k\u00f6k dosya sistemini \u00e7evrim i\u00e7i b\u00fcy\u00fctmek i\u00e7in mant\u0131ksal birim b\u00fcy\u00fcd\u00fckten sonra <code>resize2fs<\/code> kullanabilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo resize2fs \/dev\/mapper\/ubuntu--vg-ubuntu--lv\ndf -hT\nlsblk -o NAME,SIZE,FSTYPE,MOUNTPOINTS<\/code><\/pre>\n<p>Dosya sistemi XFS ise kaynak cihaz yerine ba\u011fl\u0131 oldu\u011fu mount point&#8217;i belirtin. K\u00f6k dosya sistemi i\u00e7in \u00f6rnek:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo xfs_growfs \/\ndf -hT\nlsblk -o NAME,SIZE,FSTYPE,MOUNTPOINTS<\/code><\/pre>\n<p>XFS b\u00fcy\u00fctme i\u015flemi ba\u011fl\u0131 dosya sistemi \u00fczerinde yap\u0131l\u0131r. XFS dosya sistemi k\u00fc\u00e7\u00fclt\u00fclemez; bu nedenle kapasiteyi gere\u011finden fazla b\u00fcy\u00fctmeden \u00f6nce b\u00fcy\u00fcme plan\u0131n\u0131z\u0131 belirleyin. ext4 i\u00e7in k\u00fc\u00e7\u00fcltme de b\u00fcy\u00fctmeden farkl\u0131 ve genellikle dosya sistemi ba\u011flant\u0131s\u0131n\u0131n kesilmesini gerektiren daha riskli bir i\u015flemdir. Buradaki ad\u0131mlar yaln\u0131zca b\u00fcy\u00fctme i\u00e7indir.<\/p>\n<p>Do\u011frulamada \u00fc\u00e7 \u00e7\u0131kt\u0131y\u0131 birlikte de\u011ferlendirin: <code>pvs<\/code> ile fiziksel hacim, <code>lvs<\/code> ile mant\u0131ksal birim ve <code>df -hT<\/code> ile dosya sistemi boyutu. \u0130lk iki katman b\u00fcy\u00fcm\u00fc\u015f, \u00fc\u00e7\u00fcnc\u00fc katman eski kalm\u0131\u015fsa yaln\u0131zca dosya sistemi ad\u0131m\u0131 eksiktir. <code>df<\/code> g\u00fcncellenmi\u015f fakat uygulama alan\u0131 h\u00e2l\u00e2 kullan\u0131lamaz g\u00f6r\u00fcn\u00fcyorsa inode, kota veya uygulamaya \u00f6zel depolama s\u0131n\u0131rlar\u0131n\u0131 ayr\u0131ca inceleyin.<\/p>\n<h2><span id=\"LVM_olmayan_ext4_partition8217ini_buyutme\">LVM olmayan ext4 partition&#8217;\u0131n\u0131 b\u00fcy\u00fctme<\/span><\/h2>\n<p>Do\u011frudan partition \u00fczerinde ext4 kullan\u0131yorsan\u0131z LVM komutlar\u0131na ihtiyac\u0131n\u0131z yoktur. \u00d6nce ana diskin b\u00fcy\u00fcd\u00fc\u011f\u00fcn\u00fc, ard\u0131ndan dosya sisteminin bulundu\u011fu partition&#8217;\u0131n diskin sonundaki ayr\u0131lmam\u0131\u015f alana kom\u015fu oldu\u011funu do\u011frulay\u0131n. \u00d6rnek yerle\u015fim <code>\/dev\/sda<\/code> \u00fczerinde k\u00f6k dosya sistemi olarak <code>\/dev\/sda3<\/code> olsun.<\/p>\n<p>Partition b\u00fcy\u00fctme i\u00e7in <code>growpart<\/code> kullan\u0131labilir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo growpart \/dev\/sda 3\nlsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS<\/code><\/pre>\n<p>Partition beklenen boyuta ula\u015ft\u0131ktan sonra ext4 dosya sistemini b\u00fcy\u00fct\u00fcn:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo resize2fs \/dev\/sda3\ndf -hT<\/code><\/pre>\n<p>Bu \u00f6rnekte <code>\/dev\/sda3<\/code> cihaz\u0131n\u0131 do\u011frudan kullanman\u0131z\u0131n nedeni dosya sisteminin LVM \u00fczerinde olmamas\u0131d\u0131r. Sizin <code>findmnt<\/code> \u00e7\u0131kt\u0131n\u0131z <code>\/dev\/vda1<\/code>, <code>\/dev\/nvme0n1p1<\/code> veya ba\u015fka bir cihaz g\u00f6sterebilir. \u00d6zellikle NVMe cihazlar\u0131nda partition adland\u0131rmas\u0131 farkl\u0131d\u0131r; \u00f6rnek cihaz\u0131 varsay\u0131lan kabul etmeyin.<\/p>\n<p>Dosya sistemi ba\u011fl\u0131yken b\u00fcy\u00fctme \u00e7o\u011fu ext4 kurulumunda m\u00fcmk\u00fcnd\u00fcr, ancak \u00e7ekirdek, da\u011f\u0131t\u0131m ve depolama altyap\u0131s\u0131 davran\u0131\u015f\u0131 de\u011fi\u015febilir. <code>resize2fs<\/code> hata verirse komutu tekrarlamak yerine hata metnini kaydedin, cihaz\u0131n ger\u00e7ekten ext4 oldu\u011funu ve partition boyutunun dosya sisteminden b\u00fcy\u00fck oldu\u011funu kontrol edin. \u00c7evrim d\u0131\u015f\u0131 bak\u0131m gerekiyorsa uygulamay\u0131 durdurup kurtarma ortam\u0131 veya planl\u0131 bak\u0131m prosed\u00fcr\u00fc kullan\u0131n.<\/p>\n<h2><span id=\"XFS_kullanan_sunucuda_dogru_katmani_buyutun\">XFS kullanan sunucuda do\u011fru katman\u0131 b\u00fcy\u00fct\u00fcn<\/span><\/h2>\n<p>XFS kullanan sistemlerde s\u0131k kar\u015f\u0131la\u015f\u0131lan hata, <code>resize2fs<\/code> \u00e7al\u0131\u015ft\u0131rmakt\u0131r. Bu ara\u00e7 ext ailesi i\u00e7indir; XFS i\u00e7in <code>xfs_growfs<\/code> kullan\u0131lmal\u0131d\u0131r. \u00d6nce dosya sistemi t\u00fcr\u00fcn\u00fc do\u011frulay\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">findmnt -no SOURCE,FSTYPE,TARGET \/\ndf -hT \/<\/code><\/pre>\n<p>Do\u011frudan partition \u00fczerinde XFS varsa, partition b\u00fcy\u00fctme i\u015flemi tamamland\u0131ktan sonra ba\u011fl\u0131 dosya sistemi i\u00e7in mount point&#8217;i kullan\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sudo growpart \/dev\/sda 3\nsudo xfs_growfs \/\ndf -hT \/<\/code><\/pre>\n<p>Bu \u00f6rnek yaln\u0131zca k\u00f6k dosya sistemi <code>\/dev\/sda3<\/code> ve mount point <code>\/<\/code> ise ge\u00e7erlidir. XFS bir veri diski \u00fczerinde <code>\/var\/lib<\/code> gibi ba\u015fka bir noktaya ba\u011fl\u0131ysa son komutta <code>\/var\/lib<\/code> kullan\u0131l\u0131r. LVM varsa \u00f6nce ilgili partition, PV ve LV katmanlar\u0131n\u0131 b\u00fcy\u00fct\u00fcn; <code>xfs_growfs<\/code> ancak LV yeni boyuta ula\u015ft\u0131ktan sonra \u00e7al\u0131\u015ft\u0131r\u0131lmal\u0131d\u0131r.<\/p>\n<p>XFS b\u00fcy\u00fctme s\u0131ras\u0131nda hedef mount point&#8217;in ba\u011fl\u0131 oldu\u011fundan emin olun. \u0130\u015flem sonras\u0131nda <code>df -hT<\/code> ile dosya sistemi boyutunu, uygulaman\u0131n yazabildi\u011fi ger\u00e7ek dizinde de k\u00fc\u00e7\u00fck ve kontroll\u00fc bir do\u011frulama ile kontrol edin. Test verisini \u00fcretim klas\u00f6r\u00fcnde b\u0131rakmay\u0131n ve uygulama izinlerini de\u011fi\u015ftirmeyin.<\/p>\n<div class=\"aiw-note aiw-note-tip\">\n<p class=\"aiw-box-title\">\u0130pucu<\/p>\n<p>Disk kapasitesi ile dosya sistemi kapasitesi ayn\u0131 g\u00f6stergede de\u011fildir. Disk i\u00e7in <code>lsblk<\/code>, LVM i\u00e7in <code>pvs<\/code>\/<code>lvs<\/code>, ba\u011fl\u0131 dosya sistemi i\u00e7in <code>df -hT<\/code> kullan\u0131n. Bu seviyeleri birlikte okumak, sorunun hangi katmanda kald\u0131\u011f\u0131n\u0131 ay\u0131rman\u0131z\u0131 sa\u011flar.<\/p>\n<\/div>\n<h2><span id=\"Islem_sonrasi_dogrulama_ve_geri_donus_plani\">\u0130\u015flem sonras\u0131 do\u011frulama ve geri d\u00f6n\u00fc\u015f plan\u0131<\/span><\/h2>\n<p>Alan\u0131 art\u0131rd\u0131ktan sonra yaln\u0131zca paneldeki boyuta bakmay\u0131n. A\u015fa\u011f\u0131daki kontroller, katmanlar\u0131n kapasiteyi g\u00f6rd\u00fc\u011f\u00fcn\u00fc ve uygulaman\u0131n kullan\u0131labilir alan kazand\u0131\u011f\u0131n\u0131 g\u00f6sterir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS\ndf -hT\nfindmnt -no SOURCE,FSTYPE,TARGET \/\nsudo pvs 2&gt;\/dev\/null\nsudo vgs 2&gt;\/dev\/null\nsudo lvs 2&gt;\/dev\/null<\/code><\/pre>\n<p>Yeni kapasite g\u00f6r\u00fcnmesine ra\u011fmen bo\u015f alan beklenenden azsa silinmi\u015f dosyalar\u0131n a\u00e7\u0131k dosya tan\u0131t\u0131c\u0131lar\u0131 \u00fczerinden tutulup tutulmad\u0131\u011f\u0131n\u0131 kontrol edin. Bu durum disk b\u00fcy\u00fctme i\u015fleminden ba\u011f\u0131ms\u0131z olabilir. Ayr\u0131ca inode dolulu\u011fu i\u00e7in <code>df -ih<\/code>, LVM hacim grubu i\u00e7in de <code>vgs<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 inceleyin. Uygulaman\u0131n kendi kota veya depolama ayar\u0131 varsa i\u015fletim sistemindeki bo\u015f alan uygulamaya yans\u0131mayabilir.<\/p>\n<p>Partition tablosu veya LVM boyutu \u00fczerinde yap\u0131lan de\u011fi\u015fiklikler genellikle mevcut alan\u0131 geri k\u00fc\u00e7\u00fcltmez. Yanl\u0131\u015f LV&#8217;yi b\u00fcy\u00fctt\u00fcyseniz i\u015flemi tersine \u00e7evirmek dosya sistemi t\u00fcr\u00fcne ve kullan\u0131lan alana ba\u011fl\u0131d\u0131r; XFS i\u00e7in k\u00fc\u00e7\u00fcltme yap\u0131lamaz. Bu nedenle geri d\u00f6n\u00fc\u015f, \u00e7o\u011fu zaman i\u015flem \u00f6ncesi anl\u0131k g\u00f6r\u00fcnt\u00fcye d\u00f6nmek veya yede\u011fi farkl\u0131 bir diske geri y\u00fcklemek \u015feklinde planlanmal\u0131d\u0131r.<\/p>\n<p>\u0130\u015flem s\u0131ras\u0131nda SSH ba\u011flant\u0131s\u0131 koparsa ayn\u0131 komutlar\u0131 k\u00f6rlemesine yeniden \u00e7al\u0131\u015ft\u0131rmay\u0131n. \u00d6nce yeniden ba\u011flan\u0131p <code>lsblk<\/code>, <code>pvs<\/code>, <code>lvs<\/code> ve <code>df -hT<\/code> sonu\u00e7lar\u0131n\u0131 al\u0131n. Bir ad\u0131m ba\u015far\u0131yla tamamland\u0131ysa yaln\u0131zca eksik kalan katman\u0131 tamamlay\u0131n. Komutun daha \u00f6nce \u00e7al\u0131\u015fm\u0131\u015f olmas\u0131, yanl\u0131\u015f cihaz se\u00e7imini g\u00fcvenli h\u00e2le getirmez.<\/p>\n<h2><span id=\"Sik_Sorulan_Sorular\">S\u0131k Sorulan Sorular<\/span><\/h2>\n<h3><span id=\"Sunucuyu_yeniden_baslatmadan_disk_buyutulebilir_mi\">Sunucuyu yeniden ba\u015flatmadan disk b\u00fcy\u00fct\u00fclebilir mi?<\/span><\/h3>\n<p>Bir\u00e7ok sanal disk altyap\u0131s\u0131nda disk ve dosya sistemi \u00e7evrim i\u00e7i b\u00fcy\u00fct\u00fclebilir. Ancak sanal donan\u0131m\u0131n yeni boyutu alg\u0131lamas\u0131 sa\u011flay\u0131c\u0131ya, i\u015fletim sistemine ve disk t\u00fcr\u00fcne ba\u011fl\u0131d\u0131r. <code>lsblk<\/code> eski boyutu g\u00f6steriyorsa planl\u0131 yeniden ba\u015flatma veya sa\u011flay\u0131c\u0131n\u0131n yeniden tarama prosed\u00fcr\u00fc gerekebilir.<\/p>\n<h3><span id=\"Panelde_disk_boyutu_artti_ama_du_neden_degismedi\">Panelde disk boyutu artt\u0131 ama <code>du<\/code> neden de\u011fi\u015fmedi?<\/span><\/h3>\n<p><code>du<\/code>, dizinlerdeki mevcut dosyalar\u0131n kulland\u0131\u011f\u0131 alan\u0131 toplar; bo\u015f kapasiteyi g\u00f6stermez. Kullan\u0131labilir bo\u015f alan\u0131 <code>df -hT<\/code> ile, disk ve partition boyutunu ise <code>lsblk<\/code> ile kontrol edin.<\/p>\n<h3><span id=\"Bos_alanin_tamamini_kok_LV8217ye_vermeli_miyim\">Bo\u015f alan\u0131n tamam\u0131n\u0131 k\u00f6k LV&#8217;ye vermeli miyim?<\/span><\/h3>\n<p>Hay\u0131r. K\u00f6k LV yan\u0131nda veritaban\u0131, g\u00fcnl\u00fck veya kullan\u0131c\u0131 dosyalar\u0131 i\u00e7in ayr\u0131 LV&#8217;ler varsa gelecekteki ihtiya\u00e7lar\u0131 de\u011ferlendirin. <code>+100%FREE<\/code> yaln\u0131zca t\u00fcm bo\u015f alan\u0131n se\u00e7ti\u011finiz LV&#8217;ye ayr\u0131lmas\u0131n\u0131 bilin\u00e7li olarak istiyorsan\u0131z kullan\u0131lmal\u0131d\u0131r.<\/p>\n<h3><span id=\"Dosya_sistemi_buyutuldukten_sonra_uygulamayi_yeniden_baslatmak_gerekir_mi\">Dosya sistemi b\u00fcy\u00fct\u00fcld\u00fckten sonra uygulamay\u0131 yeniden ba\u015flatmak gerekir mi?<\/span><\/h3>\n<p>Salt kapasite art\u0131\u015f\u0131nda \u00e7o\u011fu uygulama yeni bo\u015f alan\u0131 yeniden ba\u015flatma olmadan kullanabilir. Uygulama kendi kota, \u00f6nbellek veya depolama bilgisini bellekte tutuyorsa ilgili servisin dok\u00fcmantasyonuna g\u00f6re yenileme gerekebilir; bunu dosya sistemi b\u00fcy\u00fctme i\u015fleminin zorunlu bir par\u00e7as\u0131 saymay\u0131n.<\/p>\n<h2><span id=\"Uygulanabilir_kontrol_listesi\">Uygulanabilir kontrol listesi<\/span><\/h2>\n<ul>\n<li>Paneldeki disk b\u00fcy\u00fctme i\u015fleminin tamamland\u0131\u011f\u0131n\u0131 ve varsa yeniden ba\u015flatma ko\u015fulunu do\u011frulay\u0131n.<\/li>\n<li>Yedek veya anl\u0131k g\u00f6r\u00fcnt\u00fcn\u00fcn geri y\u00fcklenebilir oldu\u011funu kontrol edin.<\/li>\n<li><code>lsblk<\/code>, <code>findmnt<\/code> ve <code>df -hT<\/code> \u00e7\u0131kt\u0131lar\u0131yla ger\u00e7ek yerle\u015fimi belirleyin.<\/li>\n<li>Yeni kapasite diskte g\u00f6r\u00fcnm\u00fcyorsa partition veya dosya sistemi komutlar\u0131na ge\u00e7meyin.<\/li>\n<li>Partition&#8217;\u0131n sonundaki ayr\u0131lmam\u0131\u015f alan\u0131n ilgili partition&#8217;a kom\u015fu oldu\u011funu do\u011frulay\u0131n.<\/li>\n<li>LVM varsa partition, PV, LV ve dosya sistemi s\u0131ras\u0131n\u0131 koruyun.<\/li>\n<li>ext4 i\u00e7in <code>resize2fs<\/code>, XFS i\u00e7in <code>xfs_growfs<\/code> kullan\u0131n.<\/li>\n<li>Her katmandan sonra boyutu yeniden \u00f6l\u00e7\u00fcn ve yanl\u0131\u015f cihaz se\u00e7medi\u011finizi do\u011frulay\u0131n.<\/li>\n<li>\u0130\u015flem sonunda uygulaman\u0131n yazma yapt\u0131\u011f\u0131 ger\u00e7ek mount point \u00fczerinde g\u00fcvenli bir do\u011frulama yap\u0131n.<\/li>\n<\/ul>\n<p>Bir sonraki ad\u0131m, sunucunuzdan ilgili komutlar\u0131n yaln\u0131zca okuma ama\u00e7l\u0131 \u00e7\u0131kt\u0131lar\u0131n\u0131 almak ve hangi senaryoya ait oldu\u011funuzu kesinle\u015ftirmektir. Bu \u00e7\u0131kt\u0131 olmadan partition veya LVM komutu \u00e7al\u0131\u015ft\u0131rmak, do\u011fru y\u00f6ntemi bilseniz bile gereksiz risk olu\u015fturur.<\/p>\n<p>Bulut sunucu mimarisinin temelini netle\u015ftirmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/bulut-sunucu-nedir\/\">Bulut sunucu nedir<\/a> ifadesiyle ba\u015flayan kaynaklara, \u00f6zellikle disk kapasitesiyle birlikte IOPS ve inode ihtiya\u00e7lar\u0131n\u0131 planl\u0131yorsan\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-ve-buyuk-wordpress-siteleri-icin-disk-iops-ve-inode-planlama-rehberi\/\">disk, IOPS ve inode planlamas\u0131<\/a> ba\u015fl\u0131kl\u0131 i\u00e7eri\u011fe de bakabilirsiniz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Bulut panelinde diski b\u00fcy\u00fctmek, Linux&#8217;ta partition ve dosya sistemini otomatik b\u00fcy\u00fctmeyebilir. LVM, ext4 ve XFS i\u00e7in g\u00fcvenli uygulama ad\u0131mlar\u0131n\u0131 \u00f6\u011frenin.<\/p>\n","protected":false},"author":4,"featured_media":5784,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[34,621,625,623,60,622,624],"class_list":["post-5788","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bulut-bilisim","tag-bulut-sunucu","tag-disk-buyutme","tag-dosya-sistemi","tag-ext4","tag-linux","tag-lvm","tag-xfs"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5788","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=5788"}],"version-history":[{"count":1,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5788\/revisions"}],"predecessor-version":[{"id":5790,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5788\/revisions\/5790"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/5784"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=5788"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=5788"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=5788"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}