{"id":38936,"date":"2026-02-11T00:40:55","date_gmt":"2026-02-10T21:40:55","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=38936"},"modified":"2026-02-11T00:40:55","modified_gmt":"2026-02-10T21:40:55","slug":"ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/","title":{"rendered":"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber"},"content":{"rendered":"

<\/p>\n

Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber<\/h2>\n

Giri\u015f: NFS Nedir ve Neden Kullan\u0131l\u0131r?<\/h3>\n

NFS (Network File System), Unix tabanl\u0131 sistemler aras\u0131nda a\u011f \u00fczerinden dosya payla\u015f\u0131m\u0131n\u0131 sa\u011flayan da\u011f\u0131t\u0131k bir dosya sistemi protokol\u00fcd\u00fcr. Sun Microsystems taraf\u0131ndan 1980’lerde geli\u015ftirilen NFS, kullan\u0131c\u0131lar\u0131n bir a\u011f \u00fczerindeki uzak bilgisayarlardaki dosyalara, yerel depolama birimlerindeymi\u015f gibi eri\u015fmesine olanak tan\u0131r. Bu, \u00f6zellikle birden fazla kullan\u0131c\u0131n\u0131n veya uygulaman\u0131n ayn\u0131 verilere eri\u015fmesi gerekti\u011fi ortamlarda merkezi bir depolama \u00e7\u00f6z\u00fcm\u00fc sunar. Ubuntu 16.04, uzun s\u00fcreli destek (LTS) s\u00fcr\u00fcm\u00fc olmas\u0131 nedeniyle hala bir\u00e7ok kurumsal ve ki\u015fisel ortamda kullan\u0131lmaktad\u0131r. Bu makale, Ubuntu 16.04 \u00fczerinde bir NFS sunucusu kurma ve bir NFS istemcisini yap\u0131land\u0131rma s\u00fcre\u00e7lerini ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.<\/p>\n

NFS’in temel amac\u0131, a\u011f \u00fczerindeki makineler aras\u0131nda dosya ve dizinleri \u015feffaf bir \u015fekilde payla\u015fmakt\u0131r. Bu sayede, sunucular aras\u0131nda veri senkronizasyonu kolayla\u015f\u0131r, merkezi bir yedekleme noktas\u0131 olu\u015fturulabilir ve kullan\u0131c\u0131lar\u0131n farkl\u0131 makinelerden ayn\u0131 verilere eri\u015fimi sa\u011flan\u0131r. \u00d6rne\u011fin, bir web sunucusu k\u00fcmesi, t\u00fcm web sitelerinin dosyalar\u0131n\u0131 tek bir NFS sunucusundan \u00e7ekebilir; bu da i\u00e7eri\u011fin g\u00fcncellenmesini ve y\u00f6netilmesini b\u00fcy\u00fck \u00f6l\u00e7\u00fcde basitle\u015ftirir.<\/p>\n

NFS Kullanman\u0131n Avantajlar\u0131:<\/strong><\/p>\n

* Merkezi Veri Y\u00f6netimi:<\/strong> T\u00fcm verilerin tek bir yerde depolanmas\u0131, veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc ve yedekleme s\u00fcre\u00e7lerini kolayla\u015ft\u0131r\u0131r.
\n* Kaynak Payla\u015f\u0131m\u0131:<\/strong> Disk alan\u0131 gibi kaynaklar, a\u011f \u00fczerindeki t\u00fcm istemciler taraf\u0131ndan payla\u015f\u0131labilir, bu da depolama maliyetlerini d\u00fc\u015f\u00fcrebilir.
\n* Kolay Eri\u015fim:<\/strong> Kullan\u0131c\u0131lar, dosyalar\u0131na herhangi bir istemciden eri\u015febilir ve bu dosyalar\u0131 yerel depolamadaki dosyalar gibi kullanabilir.
\n* Y\u00f6netim Kolayl\u0131\u011f\u0131:<\/strong> Yaz\u0131l\u0131m g\u00fcncellemeleri veya yap\u0131land\u0131rma de\u011fi\u015fiklikleri gibi i\u015flemler merkezi sunucuda yap\u0131larak t\u00fcm istemcilere yans\u0131t\u0131labilir.
\n* \u00d6l\u00e7eklenebilirlik:<\/strong> \u0130htiya\u00e7 duyuldu\u011funda ek istemciler kolayca sisteme dahil edilebilir.<\/p>\n

NFS Kullanman\u0131n Dezavantajlar\u0131:<\/strong><\/p>\n

* G\u00fcvenlik Endi\u015feleri:<\/strong> Geleneksel NFSv3, zay\u0131f g\u00fcvenlik mekanizmalar\u0131na sahiptir. Veri \u015fifrelemesi ve kimlik do\u011frulama i\u00e7in ek \u00f6nlemler (VPN, Kerberos ile NFSv4) gerekebilir.
\n* Performans:<\/strong> A\u011f gecikmesi ve bant geni\u015fli\u011fi, NFS performans\u0131n\u0131 do\u011frudan etkileyebilir. \u00d6zellikle geni\u015f alan a\u011flar\u0131nda (WAN) performans d\u00fc\u015f\u00fc\u015fleri ya\u015fanabilir.
\n* Tek Ar\u0131za Noktas\u0131 (Single Point of Failure):<\/strong> NFS sunucusunun \u00e7\u00f6kmesi durumunda, t\u00fcm istemciler payla\u015f\u0131lan verilere eri\u015fimi kaybedebilir. Y\u00fcksek eri\u015filebilirlik \u00e7\u00f6z\u00fcmleri bu riski azaltabilir.<\/p>\n

Bu makalede, Ubuntu 16.04’\u00fcn kararl\u0131l\u0131\u011f\u0131 ve yayg\u0131n kullan\u0131m\u0131 g\u00f6z \u00f6n\u00fcne al\u0131narak, hem bir NFS sunucusunun nas\u0131l kurulaca\u011f\u0131 hem de bir istemcinin bu payla\u015f\u0131mlara nas\u0131l ba\u011flanaca\u011f\u0131 detayl\u0131 bir \u015fekilde ele al\u0131nacakt\u0131r.<\/p>\n

\u00d6n Gereksinimler ve Sistem Haz\u0131rl\u0131\u011f\u0131<\/h3>\n

NFS kurulumuna ba\u015flamadan \u00f6nce, baz\u0131 temel \u00f6n gereksinimlerin kar\u015f\u0131land\u0131\u011f\u0131ndan ve sistemlerin haz\u0131r oldu\u011fundan emin olmal\u0131y\u0131z. Bu rehber i\u00e7in en az iki adet Ubuntu 16.04 makinesine ihtiyac\u0131m\u0131z olacak: biri NFS sunucusu, di\u011feri NFS istemcisi olarak g\u00f6rev yapacak.<\/p>\n

Gereksinimler:<\/strong><\/p>\n

* \u0130ki Adet Ubuntu 16.04 Makinesi:<\/strong> Bu makineler fiziksel sunucular, sanal makineler (VMware, VirtualBox, KVM vb.) veya bulut \u00f6rnekleri (AWS EC2, Azure VM, Google Cloud Compute Engine vb.) olabilir.
\n* A\u011f Ba\u011flant\u0131s\u0131:<\/strong> Sunucu ve istemci makinelerinin birbirleriyle a\u011f \u00fczerinden ileti\u015fim kurabiliyor olmas\u0131 gerekir. Her iki makineye de statik IP adresleri atamak, yap\u0131land\u0131rma ve sorun giderme s\u00fcre\u00e7lerini kolayla\u015ft\u0131racakt\u0131r.
\n * \u00d6rnek Sunucu IP: 192.168.1.100<\/code>
\n * \u00d6rnek \u0130stemci IP: 192.168.1.101<\/code>
\n* Sudo Yetkileri:<\/strong> Kurulum ve yap\u0131land\u0131rma ad\u0131mlar\u0131 i\u00e7in her iki makinede de sudo<\/code> yetkilerine sahip bir kullan\u0131c\u0131 hesab\u0131na ihtiyac\u0131n\u0131z olacakt\u0131r.
\n* G\u00fcncel Sistemler:<\/strong> G\u00fcvenlik ve kararl\u0131l\u0131k a\u00e7\u0131s\u0131ndan, kurulum \u00f6ncesinde her iki sistemin de g\u00fcncel oldu\u011fundan emin olmak \u00f6nemlidir.<\/p>\n

Sistem Haz\u0131rl\u0131\u011f\u0131 Ad\u0131mlar\u0131:<\/strong><\/p>\n

Her iki makinede de a\u015fa\u011f\u0131daki komutlar\u0131 \u00e7al\u0131\u015ft\u0131rarak sistem paket listelerini g\u00fcncelleyin ve y\u00fckl\u00fc paketleri en son s\u00fcr\u00fcmlerine y\u00fckseltin:<\/p>\n

sudo apt update\nsudo apt upgrade -y<\/code><\/pre>\n
Bu i\u015flem, potansiyel g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 kapatacak ve en son paket s\u00fcr\u00fcmlerini alman\u0131z\u0131 sa\u011flayacakt\u0131r.<\/p>\n
G\u00fcvenlik Duvar\u0131 (UFW) Ayarlar\u0131:<\/strong><\/p>\n
Ubuntu’da varsay\u0131lan olarak gelen g\u00fcvenlik duvar\u0131 (UFW – Uncomplicated Firewall) etkin olabilir. NFS trafi\u011finin sorunsuz bir \u015fekilde ge\u00e7ebilmesi i\u00e7in g\u00fcvenlik duvar\u0131n\u0131 yap\u0131land\u0131rmam\u0131z gerekecektir. \u015eimdilik, kurulum tamamlanana kadar g\u00fcvenlik duvar\u0131n\u0131 ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rakabilir veya NFS i\u00e7in gerekli portlar\u0131 a\u00e7abiliriz. Kurulumun ard\u0131ndan g\u00fcvenlik duvar\u0131 ayarlar\u0131n\u0131 detayl\u0131 olarak ele alaca\u011f\u0131z.<\/p>\n
\u015eu anda UFW’nin durumunu kontrol etmek i\u00e7in:<\/p>\n
sudo ufw status<\/code><\/pre>\n
E\u011fer UFW etkinse ve varsay\u0131lan olarak gelen ba\u011flant\u0131lar\u0131 engelliyorsa, NFS ba\u011flant\u0131s\u0131 kurulurken sorun ya\u015fayabilirsiniz. Kurulumun bu a\u015famas\u0131nda, e\u011fer UFW etkinse, NFS sunucusu taraf\u0131nda gerekli portlar\u0131 a\u00e7maya odaklanaca\u011f\u0131z. \u0130stemci taraf\u0131nda genellikle \u00f6zel bir UFW ayar\u0131 gerekmez, \u00e7\u00fcnk\u00fc istemci sunucuya ba\u011flant\u0131 ba\u015flat\u0131r.<\/p>\n
Bu \u00f6n haz\u0131rl\u0131klar tamamland\u0131ktan sonra, NFS sunucusu kurulumuna ge\u00e7ebiliriz.<\/p>\n
NFS Sunucu Kurulumu ve Yap\u0131land\u0131rmas\u0131<\/h3>\n
NFS sunucusu, payla\u015f\u0131lan dizinleri bar\u0131nd\u0131racak ve istemcilere bu dizinlere eri\u015fim sa\u011flayacak makinedir. Kurulum s\u00fcreci, gerekli paketlerin y\u00fcklenmesini, payla\u015f\u0131lacak dizinin olu\u015fturulmas\u0131n\u0131, \/etc\/exports<\/code> dosyas\u0131n\u0131n yap\u0131land\u0131r\u0131lmas\u0131n\u0131 ve g\u00fcvenlik duvar\u0131 ayarlar\u0131n\u0131n yap\u0131lmas\u0131n\u0131 i\u00e7erir.<\/p>\n
NFS Sunucu Paketlerinin Kurulumu<\/h4>\n
NFS sunucusunu kurmak i\u00e7in nfs-kernel-server<\/code> paketini y\u00fcklememiz gerekir. Bu paket, NFS \u00e7ekirdek mod\u00fcllerini ve ilgili yard\u0131mc\u0131 programlar\u0131 i\u00e7erir.<\/p>\n
NFS sunucusu olarak kullanaca\u011f\u0131n\u0131z makinede a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n
sudo apt install nfs-kernel-server -y<\/code><\/pre>\n
Kurulum tamamland\u0131\u011f\u0131nda, NFS servisi otomatik olarak ba\u015flayacakt\u0131r. Servisin durumunu kontrol etmek i\u00e7in:<\/p>\n
systemctl status nfs-kernel-server<\/code><\/pre>\n
\u00c7\u0131kt\u0131da active (exited)<\/code> veya active (running)<\/code> ibaresini g\u00f6rmelisiniz.<\/p>\n
Payla\u015f\u0131lacak Dizinin Olu\u015fturulmas\u0131 ve \u0130zinlerin Ayarlanmas\u0131<\/h4>\n
\u015eimdi, NFS istemcileriyle payla\u015fmak istedi\u011fimiz dizini olu\u015ftural\u0131m. Bu dizin, istemcilerin eri\u015fece\u011fi merkezi depolama alan\u0131 olacakt\u0131r. Genellikle \/mnt<\/code> veya \/srv<\/code> alt\u0131nda bir dizin olu\u015fturulur.<\/p>\n
\u00d6rnek olarak \/mnt\/nfs_share<\/code> ad\u0131nda bir dizin olu\u015ftural\u0131m:<\/p>\n
sudo mkdir -p \/mnt\/nfs_share<\/code><\/pre>\n
Bu dizine, istemcilerin dosya olu\u015fturabilmesi ve de\u011fi\u015ftirebilmesi i\u00e7in uygun izinler vermemiz gerekebilir. E\u011fer t\u00fcm kullan\u0131c\u0131lar\u0131n tam eri\u015fime sahip olmas\u0131n\u0131 istiyorsan\u0131z, dizinin sahipli\u011fini ve izinlerini ayarlayabilirsiniz. \u00d6rne\u011fin, herkesin okuma, yazma ve \u00e7al\u0131\u015ft\u0131rma iznine sahip olmas\u0131n\u0131 sa\u011flamak i\u00e7in:<\/p>\n
sudo chown nobody:nogroup \/mnt\/nfs_share\nsudo chmod 777 \/mnt\/nfs_share<\/code><\/pre>\n
*   chown nobody:nogroup<\/code>: Bu komut, dizinin sahibini nobody<\/code> kullan\u0131c\u0131s\u0131 ve nogroup<\/code> grubuna atar. Bu, genellikle NFS payla\u015f\u0131mlar\u0131 i\u00e7in iyi bir uygulamad\u0131r, \u00e7\u00fcnk\u00fc istemciden gelen root d\u0131\u015f\u0131 kullan\u0131c\u0131lar\u0131n kimlikleri, sunucudaki nobody<\/code> kullan\u0131c\u0131s\u0131na e\u015flenecektir (squashing).
\n*   chmod 777<\/code>: Bu komut, dizine tam okuma, yazma ve \u00e7al\u0131\u015ft\u0131rma izinleri verir. Ger\u00e7ek bir \u00fcretim ortam\u0131nda, daha k\u0131s\u0131tl\u0131 izinler (\u00f6rne\u011fin, belirli bir kullan\u0131c\u0131 veya grup i\u00e7in) vermek isteyebilirsiniz.<\/p>\n
NFS D\u0131\u015fa Aktarma Listesinin Yap\u0131land\u0131r\u0131lmas\u0131 (\/etc\/exports<\/code>)<\/h4>\n
\/etc\/exports<\/code> dosyas\u0131, NFS sunucusunun hangi dizinleri, hangi istemcilere ve hangi se\u00e7eneklerle payla\u015faca\u011f\u0131n\u0131 tan\u0131mlad\u0131\u011f\u0131 ana yap\u0131land\u0131rma dosyas\u0131d\u0131r. Bu dosyay\u0131 d\u00fczenleyerek payla\u015f\u0131mlar\u0131m\u0131z\u0131 tan\u0131mlayaca\u011f\u0131z.<\/p>\n
Dosyay\u0131 bir metin d\u00fczenleyici ile a\u00e7\u0131n:<\/p>\n
sudo nano \/etc\/exports<\/code><\/pre>\n
Dosyan\u0131n sonuna a\u015fa\u011f\u0131daki gibi bir sat\u0131r ekleyin:<\/p>\n
\/mnt\/nfs_share    192.168.1.101(rw,sync,no_subtree_check)<\/code><\/pre>\n
Bu sat\u0131r\u0131 a\u00e7\u0131klayal\u0131m:<\/p>\n
*   \/mnt\/nfs_share<\/code>: Payla\u015f\u0131lacak olan yerel dizinin yolu.
\n   192.168.1.101<\/code>: Bu dizine eri\u015fim izni verilecek olan istemcinin IP adresidir. Birden fazla istemci i\u00e7in virg\u00fclle ayr\u0131lm\u0131\u015f IP adresleri veya bir a\u011f aral\u0131\u011f\u0131 (\u00f6rne\u011fin, 192.168.1.0\/24<\/code>) belirtebilirsiniz. <\/em><\/code> kullanarak t\u00fcm istemcilere izin verebilirsiniz, ancak g\u00fcvenlik a\u00e7\u0131s\u0131ndan bu \u00f6nerilmez.
\n*   (...)<\/code>: Parantez i\u00e7indeki k\u0131s\u0131m, bu payla\u015f\u0131m i\u00e7in ge\u00e7erli olacak se\u00e7eneklerdir.
\n    *   rw<\/code>: (Read\/Write) \u0130stemciye payla\u015f\u0131lan dizine hem okuma hem de yazma izni verir. Sadece okuma izni vermek isterseniz ro<\/code> (Read Only) kullan\u0131n.
\n    *   sync<\/code>: NFS’in senkronize modda \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar. Bu, bir yazma i\u015flemi tamamland\u0131\u011f\u0131nda, verilerin diske ger\u00e7ekten yaz\u0131ld\u0131\u011f\u0131n\u0131 garanti eder. Performans\u0131 bir miktar d\u00fc\u015f\u00fcrebilir ancak veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc art\u0131r\u0131r. Alternatifi async<\/code>‘tir, bu daha h\u0131zl\u0131d\u0131r ancak g\u00fc\u00e7 kesintisi gibi durumlarda veri kayb\u0131 riski ta\u015f\u0131r.
\n    *   no_subtree_check<\/code>: Alt dizin kontrollerini devre d\u0131\u015f\u0131 b\u0131rak\u0131r. Bu, \u00f6zellikle bir dizinin bir b\u00f6l\u00fcm\u00fc payla\u015f\u0131l\u0131yorsa, performans sorunlar\u0131n\u0131 \u00f6nler ve genellikle \u00f6nerilen bir se\u00e7enektir.
\n    *   no_root_squash<\/code>: Bu se\u00e7enek, istemcideki root<\/code> kullan\u0131c\u0131s\u0131n\u0131n sunucudaki root<\/code> kullan\u0131c\u0131s\u0131 gibi muamele g\u00f6rmesini sa\u011flar. Bu g\u00fcvenlik a\u00e7\u0131s\u0131ndan \u00e7ok risklidir ve yaln\u0131zca g\u00fcvendi\u011finiz istemciler ve belirli durumlar i\u00e7in kullan\u0131lmal\u0131d\u0131r.<\/strong> Varsay\u0131lan olarak root_squash<\/code> etkindir, bu da istemcideki root<\/code> kullan\u0131c\u0131s\u0131n\u0131n kimli\u011fini nobody<\/code> kullan\u0131c\u0131s\u0131na e\u015fler.
\n    *   all_squash<\/code>: T\u00fcm istemci kullan\u0131c\u0131lar\u0131n\u0131n kimliklerini sunucudaki nobody<\/code> kullan\u0131c\u0131s\u0131na e\u015fler. Bu, ek bir g\u00fcvenlik katman\u0131 sa\u011flar.
\n    *   anonuid=ID<\/code> ve anongid=ID<\/code>: root_squash<\/code> veya all_squash<\/code> kullan\u0131ld\u0131\u011f\u0131nda, nobody<\/code> kullan\u0131c\u0131s\u0131n\u0131n UID’sini ve GID’sini belirleyebilirsiniz. Varsay\u0131lan olarak nobody<\/code> (UID=65534, GID=65534) kullan\u0131l\u0131r.<\/p>\n
\u00d6rnek \/etc\/exports<\/code> yap\u0131land\u0131rmalar\u0131:<\/p>\n
# Belirli bir istemciye okuma\/yazma izni\n\/mnt\/nfs_share    192.168.1.101(rw,sync,no_subtree_check)\n\n
Bir a\u011f aral\u0131\u011f\u0131na sadece okuma izni<\/h2>\n\/srv\/read_only    192.168.1.0\/24(ro,sync,no_subtree_check)\n\n
Birden fazla istemciye farkl\u0131 se\u00e7eneklerle eri\u015fim<\/h2>\n\/home\/users       192.168.1.102(rw,sync,no_subtree_check) 192.168.1.103(ro,sync,no_subtree_check)\n\n
T\u00fcm istemcilere okuma\/yazma, t\u00fcm kullan\u0131c\u0131lar\u0131 nobody olarak e\u015fle<\/h2>\n\/var\/www\/html     *(rw,sync,no_subtree_check,all_squash)<\/code><\/pre>\n
Yap\u0131land\u0131rma dosyas\u0131n\u0131 kaydettikten sonra (Ctrl+O<\/code>, Enter<\/code>, Ctrl+X<\/code> nano’da), NFS sunucusuna yeni d\u0131\u015fa aktarmalar\u0131 okumas\u0131n\u0131 s\u00f6ylememiz gerekir.<\/p>\n
NFS Sunucusunu Yeniden Ba\u015flatma ve D\u0131\u015fa Aktar\u0131mlar\u0131 Kontrol Etme<\/h4>\n
\/etc\/exports<\/code> dosyas\u0131nda yapt\u0131\u011f\u0131n\u0131z de\u011fi\u015fikliklerin etkin olmas\u0131 i\u00e7in NFS sunucusunu yeniden ba\u015flatman\u0131z veya exportfs<\/code> komutunu \u00e7al\u0131\u015ft\u0131rman\u0131z gerekir.<\/p>\n
De\u011fi\u015fiklikleri uygulamak i\u00e7in:<\/p>\n
sudo exportfs -a<\/code><\/pre>\n
Bu komut, \/etc\/exports<\/code> dosyas\u0131ndaki t\u00fcm payla\u015f\u0131mlar\u0131 yeniden d\u0131\u015fa aktar\u0131r. -r<\/code> (yeniden d\u0131\u015fa aktar) ve -v<\/code> (ayr\u0131nt\u0131l\u0131 \u00e7\u0131kt\u0131) se\u00e7eneklerini de kullanabilirsiniz:<\/p>\n
sudo exportfs -rv<\/code><\/pre>\n
NFS servisini yeniden ba\u015flatmak da ayn\u0131 etkiyi yarat\u0131r ve bazen daha g\u00fcvenli bir y\u00f6ntem olabilir:<\/p>\n
sudo systemctl restart nfs-kernel-server<\/code><\/pre>\n
D\u0131\u015fa aktar\u0131mlar\u0131n\u0131z\u0131n do\u011fru bir \u015fekilde yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in showmount<\/code> komutunu kullanabilirsiniz:<\/p>\n
showmount -e localhost<\/code><\/pre>\n
Bu komut, sunucunun d\u0131\u015fa aktard\u0131\u011f\u0131 dizinleri listelemelidir. \u00d6rnek \u00e7\u0131kt\u0131:<\/p>\n
Export list for localhost:\n\/mnt\/nfs_share 192.168.1.101<\/code><\/pre>\n
G\u00fcvenlik Duvar\u0131 Ayarlar\u0131 (UFW)<\/h4>\n
NFS, \u00e7e\u015fitli portlar\u0131 kullan\u0131r. Temel NFS trafi\u011fi i\u00e7in 2049\/TCP ve 2049\/UDP portlar\u0131 kullan\u0131l\u0131rken, RPC (Remote Procedure Call) hizmetleri (NFS’in ba\u011f\u0131ml\u0131 oldu\u011fu) 111\/TCP ve 111\/UDP portlar\u0131n\u0131 kullan\u0131r. Ayr\u0131ca, NFS taraf\u0131ndan dinamik olarak atanan portlar da olabilir (mountd, statd, lockd gibi).<\/p>\n
G\u00fcvenli bir yap\u0131land\u0131rma i\u00e7in, sadece belirli istemci IP adreslerinden gelen NFS trafi\u011fine izin vermek en iyi uygulamad\u0131r.<\/p>\n
NFS sunucusu \u00fczerinde, istemcinin IP adresinden (\u00f6rne\u011fimizde 192.168.1.101<\/code>) gelen ba\u011flant\u0131lara izin vermek i\u00e7in UFW kurallar\u0131n\u0131 ekleyin:<\/p>\n
sudo ufw allow from 192.168.1.101 to any port nfs\nsudo ufw allow from 192.168.1.101 to any port rpcbind<\/code><\/pre>\n
nfs<\/code> ve rpcbind<\/code> servisleri UFW taraf\u0131ndan tan\u0131nan servislerdir ve ilgili portlar\u0131 otomatik olarak a\u00e7ar. E\u011fer UFW varsay\u0131lan olarak kapal\u0131ysa, bu komutlar bir hata vermez ancak kurallar\u0131 ekler. E\u011fer UFW daha \u00f6nce etkin de\u011filse, etkinle\u015ftirmelisiniz:<\/p>\n
sudo ufw enable<\/code><\/pre>\n
Bu komut, UFW’yi etkinle\u015ftirir ve mevcut kurallar\u0131 uygular. Etkinle\u015ftirmeden \u00f6nce SSH ba\u011flant\u0131n\u0131z\u0131 kaybetmemek i\u00e7in SSH portuna (varsay\u0131lan 22) izin verdi\u011finizden emin olun:<\/p>\n
sudo ufw allow ssh<\/code><\/pre>\n
UFW durumunu kontrol etmek i\u00e7in:<\/p>\n
sudo ufw status verbose<\/code><\/pre>\n
\u00c7\u0131kt\u0131da, ekledi\u011finiz kurallar\u0131 ve durumun active<\/code> oldu\u011funu g\u00f6rmelisiniz.<\/p>\n
NFS sunucusu yap\u0131land\u0131rmas\u0131 bu noktada tamamlanm\u0131\u015ft\u0131r. \u015eimdi NFS istemcisi kurulumuna ge\u00e7ebiliriz.<\/p>\n
NFS \u0130stemci Kurulumu ve Yap\u0131land\u0131rmas\u0131<\/h3>\n
NFS istemcisi, NFS sunucusunda payla\u015f\u0131lan dizinlere eri\u015fecek makinedir. \u0130stemci taraf\u0131nda da gerekli paketlerin y\u00fcklenmesi ve payla\u015f\u0131mlar\u0131n ba\u011flanmas\u0131 ad\u0131mlar\u0131 bulunur.<\/p>\n
NFS \u0130stemci Paketlerinin Kurulumu<\/h4>\n
NFS istemcisi olarak kullanaca\u011f\u0131n\u0131z makinede, NFS payla\u015f\u0131mlar\u0131na ba\u011flanmak i\u00e7in nfs-common<\/code> paketini y\u00fcklemeniz gerekir. Bu paket, NFS istemci yard\u0131mc\u0131 programlar\u0131n\u0131 ve k\u00fct\u00fcphanelerini i\u00e7erir.<\/p>\n
NFS istemcisi olarak kullanaca\u011f\u0131n\u0131z makinede a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n
sudo apt install nfs-common -y<\/code><\/pre>\n
Kurulum tamamland\u0131\u011f\u0131nda, istemci makineniz NFS payla\u015f\u0131mlar\u0131na ba\u011flanmaya haz\u0131r olacakt\u0131r.<\/p>\n
Payla\u015f\u0131lan Dizinin \u0130stemci \u00dczerine Ba\u011flanmas\u0131<\/h4>\n
NFS sunucusundan d\u0131\u015fa aktar\u0131lan dizini istemci makinesine ba\u011flamadan \u00f6nce, sunucunun payla\u015f\u0131mlar\u0131n\u0131 kontrol etmek iyi bir uygulamad\u0131r.<\/p>\n
\u0130stemci makinesinde, NFS sunucusunun IP adresini kullanarak hangi dizinleri d\u0131\u015fa aktard\u0131\u011f\u0131n\u0131 kontrol edin:<\/p>\n
showmount -e 192.168.1.100<\/code><\/pre>\n
Burada 192.168.1.100<\/code> NFS sunucunuzun IP adresidir. \u00c7\u0131kt\u0131, sunucunun d\u0131\u015fa aktard\u0131\u011f\u0131 dizinleri ve hangi istemcilerin eri\u015febilece\u011fini g\u00f6stermelidir:<\/p>\n
Export list for 192.168.1.100:\n\/mnt\/nfs_share 192.168.1.101<\/code><\/pre>\n
\u015eimdi, payla\u015f\u0131lan dizini ba\u011flayaca\u011f\u0131m\u0131z bir yerel ba\u011flama noktas\u0131 olu\u015fturmam\u0131z gerekiyor. Bu genellikle \/mnt<\/code> veya \/media<\/code> alt\u0131nda bir dizin olur.<\/p>\n
sudo mkdir -p \/mnt\/nfs_share_client<\/code><\/pre>\n
Ard\u0131ndan, NFS sunucusundaki dizini istemci makinesindeki bu ba\u011flama noktas\u0131na ba\u011flay\u0131n:<\/p>\n
sudo mount -t nfs 192.168.1.100:\/mnt\/nfs_share \/mnt\/nfs_share_client<\/code><\/pre>\n
*   -t nfs<\/code>: Ba\u011flanacak dosya sisteminin t\u00fcr\u00fcn\u00fc NFS olarak belirtir.
\n*   192.168.1.100:\/mnt\/nfs_share<\/code>: NFS sunucusunun IP adresi ve sunucudaki payla\u015f\u0131lan dizinin yoludur.
\n*   \/mnt\/nfs_share_client<\/code>: \u0130stemci makinesindeki ba\u011flama noktas\u0131d\u0131r.<\/p>\n
Ba\u011flama i\u015flemi ba\u015far\u0131l\u0131 olursa, herhangi bir \u00e7\u0131kt\u0131 vermeyecektir. Ba\u011flant\u0131n\u0131n ba\u015far\u0131l\u0131 oldu\u011funu do\u011frulamak i\u00e7in df -h<\/code> komutunu kullanabilirsiniz:<\/p>\n
df -h<\/code><\/pre>\n
\u00c7\u0131kt\u0131da, 192.168.1.100:\/mnt\/nfs_share<\/code> adresinin \/mnt\/nfs_share_client<\/code> ba\u011flama noktas\u0131na ba\u011fland\u0131\u011f\u0131n\u0131 g\u00f6rmelisiniz.<\/p>\n
\u00d6rnek \u00e7\u0131kt\u0131:<\/p>\n
Filesystem                         Size  Used Avail Use% Mounted on\n...\n192.168.1.100:\/mnt\/nfs_share       9.8G  1.2G  8.6G  13% \/mnt\/nfs_share_client<\/code><\/pre>\n
Ba\u011flant\u0131y\u0131 test etmek i\u00e7in, istemci \u00fczerindeki \/mnt\/nfs_share_client<\/code> dizinine bir dosya olu\u015fturmay\u0131 deneyin:<\/p>\n
sudo touch \/mnt\/nfs_share_client\/test_file.txt\nls -l \/mnt\/nfs_share_client\/<\/code><\/pre>\n
\u015eimdi NFS sunucusuna giderek \/mnt\/nfs_share<\/code> dizininde bu dosyan\u0131n g\u00f6r\u00fcn\u00fcp g\u00f6r\u00fcnmedi\u011fini kontrol edin:<\/p>\n
ls -l \/mnt\/nfs_share\/<\/code><\/pre>\n
E\u011fer dosya her iki tarafta da g\u00f6r\u00fcn\u00fcyorsa ve istemciden yazma izniniz varsa, NFS ba\u011flant\u0131s\u0131 ba\u015far\u0131yla kurulmu\u015f demektir.<\/p>\n
Sistem Ba\u015flang\u0131c\u0131nda Otomatik Ba\u011flant\u0131 (\/etc\/fstab<\/code>)<\/h4>\n
Yukar\u0131daki mount<\/code> komutuyla yap\u0131lan ba\u011flant\u0131, sistem yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda kaybolacakt\u0131r. NFS payla\u015f\u0131m\u0131n\u0131n her zaman eri\u015filebilir olmas\u0131 i\u00e7in, sistemi ba\u015flang\u0131c\u0131nda otomatik olarak ba\u011flanmas\u0131n\u0131 sa\u011flayacak \u015fekilde \/etc\/fstab<\/code> dosyas\u0131n\u0131 d\u00fczenlememiz gerekir.<\/p>\n
\u0130stemci makinesinde \/etc\/fstab<\/code> dosyas\u0131n\u0131 a\u00e7\u0131n:<\/p>\n
sudo nano \/etc\/fstab<\/code><\/pre>\n
Dosyan\u0131n sonuna a\u015fa\u011f\u0131daki sat\u0131r\u0131 ekleyin:<\/p>\n
192.168.1.100:\/mnt\/nfs_share    \/mnt\/nfs_share_client    nfs    defaults,_netdev    0    0<\/code><\/pre>\n
Bu sat\u0131r\u0131 a\u00e7\u0131klayal\u0131m:<\/p>\n
*   192.168.1.100:\/mnt\/nfs_share<\/code>: NFS sunucusunun IP adresi ve payla\u015f\u0131lan dizinin yolu.
\n*   \/mnt\/nfs_share_client<\/code>: \u0130stemci \u00fczerindeki ba\u011flama noktas\u0131.
\n*   nfs<\/code>: Dosya sistemi t\u00fcr\u00fc.
\n*   defaults,_netdev<\/code>: Ba\u011flama se\u00e7enekleri.
\n    *   defaults<\/code>: Genellikle rw,suid,dev,exec,auto,nouser,async<\/code> se\u00e7eneklerinin birle\u015fimidir.
\n    *   _netdev<\/code>: Bu se\u00e7enek, bu dosya sisteminin bir a\u011f cihaz\u0131 oldu\u011funu ve a\u011f servisleri ba\u015flat\u0131lana kadar ba\u011flanmamas\u0131 gerekti\u011fini belirtir. Bu, a\u011f ba\u011flant\u0131s\u0131 hen\u00fcz kurulmadan NFS’in ba\u011flanmaya \u00e7al\u0131\u015fmas\u0131n\u0131 ve \u00f6ny\u00fckleme s\u0131ras\u0131nda tak\u0131l\u0131 kalmas\u0131n\u0131 \u00f6nler. Ubuntu 16.04 i\u00e7in kritik bir se\u00e7enektir.<\/strong>
\n*   0<\/code>: Dump arac\u0131 taraf\u0131ndan yedeklenip yedeklenmeyece\u011fini belirtir (0 = yedekleme yapma).
\n*   0<\/code>: fsck<\/code> arac\u0131 taraf\u0131ndan dosya sistemi kontrol\u00fcn\u00fcn s\u0131ras\u0131n\u0131 belirtir (0 = kontrol etme).<\/p>\n
\/etc\/fstab<\/code> dosyas\u0131n\u0131 kaydettikten sonra, sisteminizi yeniden ba\u015flatmadan \u00f6nce yeni fstab girdisini test etmek iyi bir uygulamad\u0131r. Mevcut NFS ba\u011flant\u0131s\u0131n\u0131 kald\u0131r\u0131n (e\u011fer ba\u011fl\u0131ysa) ve ard\u0131ndan fstab’daki t\u00fcm girdileri ba\u011flamay\u0131 deneyin:<\/p>\n
sudo umount \/mnt\/nfs_share_client\nsudo mount -a<\/code><\/pre>\n
umount<\/code> komutu ba\u011flant\u0131y\u0131 keser. mount -a<\/code> komutu, \/etc\/fstab<\/code> dosyas\u0131nda listelenen ve zaten ba\u011fl\u0131 olmayan t\u00fcm dosya sistemlerini ba\u011flamaya \u00e7al\u0131\u015f\u0131r. E\u011fer bu komut herhangi bir hata vermezse ve df -h<\/code> \u00e7\u0131kt\u0131s\u0131nda NFS payla\u015f\u0131m\u0131n\u0131 tekrar g\u00f6r\u00fcyorsan\u0131z, \/etc\/fstab<\/code> yap\u0131land\u0131rman\u0131z do\u011fru demektir.<\/p>\n
\u015eimdi sisteminizi yeniden ba\u015flatabilir ve NFS payla\u015f\u0131m\u0131n\u0131n otomatik olarak ba\u011flan\u0131p ba\u011flanmad\u0131\u011f\u0131n\u0131 kontrol edebilirsiniz.<\/p>\n
NFS Ba\u011flant\u0131s\u0131n\u0131n Test Edilmesi ve Sorun Giderme<\/h3>\n
NFS ba\u011flant\u0131s\u0131n\u0131 ba\u015far\u0131yla kurduktan sonra, beklendi\u011fi gibi \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak i\u00e7in \u00e7e\u015fitli testler yapmak ve olas\u0131 sorunlarla ba\u015fa \u00e7\u0131kmak \u00f6nemlidir.<\/p>\n
Temel Testler<\/h4>\n
1.  Dosya Olu\u015fturma ve Silme:<\/strong> \u0130stemci makinesinde, NFS ba\u011flama noktas\u0131 (\u00f6rne\u011fin \/mnt\/nfs_share_client<\/code>) i\u00e7inde bir dosya olu\u015fturun, i\u00e7ine veri yaz\u0131n ve ard\u0131ndan silmeyi deneyin.<\/p>\n
echo \"Bu bir test dosyas\u0131d\u0131r.\" | sudo tee \/mnt\/nfs_share_client\/istemci_test.txt\n    cat \/mnt\/nfs_share_client\/istemci_test.txt\n    sudo rm \/mnt\/nfs_share_client\/istemci_test.txt<\/code><\/pre>\n
    Bu i\u015flemleri ba\u015far\u0131yla yapabiliyorsan\u0131z, okuma\/yazma izinleriniz do\u011fru demektir.
\n2.  Sunucu Taraf\u0131nda Do\u011frulama:<\/strong> \u0130stemcide yapt\u0131\u011f\u0131n\u0131z de\u011fi\u015fikliklerin NFS sunucusunda da yans\u0131t\u0131ld\u0131\u011f\u0131n\u0131 kontrol edin. \u00d6rne\u011fin, istemcide olu\u015fturdu\u011funuz istemci_test.txt<\/code> dosyas\u0131n\u0131n sunucudaki \/mnt\/nfs_share<\/code> dizininde g\u00f6r\u00fcn\u00fcp g\u00f6r\u00fcnmedi\u011fini kontrol edin.
\n3.  Performans Testi:<\/strong> B\u00fcy\u00fck bir dosyay\u0131 (\u00f6rne\u011fin birka\u00e7 y\u00fcz MB veya GB) NFS payla\u015f\u0131m\u0131na kopyalayarak performans\u0131 test edebilirsiniz. Bu, a\u011f h\u0131z\u0131n\u0131z\u0131 ve NFS yap\u0131land\u0131rman\u0131z\u0131n etkinli\u011fini g\u00f6sterir.<\/p>\n
# \u00d6rnek olarak 1GB boyutunda bir dosya olu\u015ftur\n    dd if=\/dev\/zero of=\/tmp\/large_file.img bs=1M count=1024\n    # Bu dosyay\u0131 NFS payla\u015f\u0131m\u0131na kopyala\n    time cp \/tmp\/large_file.img \/mnt\/nfs_share_client\/<\/code><\/pre>\n
    time<\/code> komutu, kopyalama i\u015fleminin ne kadar s\u00fcrd\u00fc\u011f\u00fcn\u00fc g\u00f6sterecektir.<\/p>\n
Yayg\u0131n Sorunlar ve \u00c7\u00f6z\u00fcmleri<\/h4>\n
NFS kurulumu s\u0131ras\u0131nda veya sonras\u0131nda kar\u015f\u0131la\u015fabilece\u011finiz baz\u0131 yayg\u0131n sorunlar ve bunlar\u0131n olas\u0131 \u00e7\u00f6z\u00fcmleri a\u015fa\u011f\u0131da listelenmi\u015ftir:<\/p>\n
1.  mount: ... No route to host<\/code> veya mount: ... Connection refused<\/code>:<\/strong>
\n    *   Neden:<\/strong> Sunucuya a\u011f ba\u011flant\u0131s\u0131 yok veya g\u00fcvenlik duvar\u0131 engelliyor.
\n    *   \u00c7\u00f6z\u00fcm:<\/strong>
\n        *   \u0130stemciden sunucuya ping<\/code> atarak a\u011f ba\u011flant\u0131s\u0131n\u0131 kontrol edin: ping 192.168.1.100<\/code>.
\n        *   NFS sunucusunda UFW veya ba\u015fka bir g\u00fcvenlik duvar\u0131n\u0131n NFS portlar\u0131n\u0131 (2049, 111) ve RPC portlar\u0131n\u0131 istemci IP’sine a\u00e7t\u0131\u011f\u0131ndan emin olun. sudo ufw status verbose<\/code> komutuyla kontrol edin.
\n        *   Sunucu \u00fczerinde nfs-kernel-server<\/code> ve rpcbind<\/code> servislerinin \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun: systemctl status nfs-kernel-server<\/code> ve systemctl status rpcbind<\/code>.<\/p>\n
2.  mount: ... Permission denied<\/code>:<\/strong>
\n    *   Neden:<\/strong> \u0130stemcinin payla\u015f\u0131ma eri\u015fim izni yok veya exports<\/code> dosyas\u0131nda yanl\u0131\u015f yap\u0131land\u0131rma var.
\n    *   \u00c7\u00f6z\u00fcm:<\/strong>
\n        *   NFS sunucusundaki \/etc\/exports<\/code> dosyas\u0131n\u0131 kontrol edin. \u0130stemcinin IP adresinin do\u011fru yaz\u0131ld\u0131\u011f\u0131ndan ve rw<\/code> (okuma\/yazma) veya ro<\/code> (sadece okuma) izninin verildi\u011finden emin olun.
\n        *   sudo exportfs -rv<\/code> komutunu \u00e7al\u0131\u015ft\u0131rarak de\u011fi\u015fiklikleri uygulay\u0131n ve showmount -e localhost<\/code> ile kontrol edin.
\n        *   Sunucu taraf\u0131ndaki payla\u015f\u0131lan dizinin (\u00f6rn. \/mnt\/nfs_share<\/code>) izinlerini ve sahipli\u011fini kontrol edin (ls -ld \/mnt\/nfs_share<\/code>). \u0130stemcinin yazma iznine sahip olabilmesi i\u00e7in genellikle 777<\/code> veya uygun bir kullan\u0131c\u0131\/grup izinleri gerekir.<\/p>\n
3.  UID\/GID E\u015fle\u015fmeme Sorunlar\u0131:<\/strong>
\n    *   Neden:<\/strong> \u0130stemci ve sunucu \u00fczerindeki kullan\u0131c\u0131 ve grup kimlikleri (UID\/GID) e\u015fle\u015fmedi\u011finde, dosya sahiplikleri ve izinleri yanl\u0131\u015f g\u00f6r\u00fcnebilir veya eri\u015fim sorunlar\u0131 ya\u015fanabilir.
\n    *   \u00c7\u00f6z\u00fcm:<\/strong>
\n        *   En basit \u00e7\u00f6z\u00fcm, \/etc\/exports<\/code> dosyas\u0131nda all_squash<\/code> se\u00e7ene\u011fini kullanmakt\u0131r. Bu, t\u00fcm istemci kullan\u0131c\u0131lar\u0131n\u0131 sunucudaki nobody<\/code> kullan\u0131c\u0131s\u0131na e\u015fler.
\n        *   Daha kontroll\u00fc bir \u00e7\u00f6z\u00fcm, istemci ve sunucu \u00fczerinde ayn\u0131 UID\/GID’ye sahip kullan\u0131c\u0131lar ve gruplar olu\u015fturmakt\u0131r. \u00d6rne\u011fin, sunucuda nfsuser<\/code> (UID=1001) olu\u015fturup, istemcide de ayn\u0131 UID’ye sahip bir nfsuser<\/code> olu\u015fturmak.
\n        *   no_root_squash<\/code> kullanmaktan ka\u00e7\u0131n\u0131n, zira bu g\u00fcvenlik riskleri ta\u015f\u0131r.<\/p>\n
4.  mount -a<\/code> komutu boot s\u0131ras\u0131nda tak\u0131l\u0131yor veya hata veriyor:<\/strong>
\n    *   Neden:<\/strong> \/etc\/fstab<\/code> dosyas\u0131ndaki NFS girdisi, a\u011f servisleri ba\u015flamadan \u00f6nce ba\u011flanmaya \u00e7al\u0131\u015f\u0131yor.
\n    *   \u00c7\u00f6z\u00fcm:<\/strong>
\n        *   \/etc\/fstab<\/code> girdinizde _netdev<\/code> se\u00e7ene\u011finin oldu\u011fundan emin olun:<\/p>\n
192.168.1.100:\/mnt\/nfs_share    \/mnt\/nfs_share_client    nfs    defaults,_netdev    0    0<\/code><\/pre>\n
        *   Ayr\u0131ca, ba\u011flant\u0131 sorunlar\u0131 durumunda sistemin tak\u0131lmas\u0131n\u0131 \u00f6nlemek i\u00e7in hard<\/code> yerine soft<\/code> ve intr<\/code> (kesilebilir) se\u00e7eneklerini kullanmay\u0131 d\u00fc\u015f\u00fcnebilirsiniz:<\/p>\n
192.168.1.100:\/mnt\/nfs_share    \/mnt\/nfs_share_client    nfs    defaults,_netdev,soft,intr    0    0<\/code><\/pre>\n
            *   hard<\/code>: NFS sunucusu yan\u0131t vermezse, istemci tekrar tekrar denemeye devam eder ve i\u015flem kilitlenir.
\n            *   soft<\/code>: NFS sunucusu yan\u0131t vermezse, istemci belirli bir s\u00fcre sonra hata d\u00f6nd\u00fcr\u00fcr.
\n            *   intr<\/code>: hard<\/code> mount’lar i\u00e7in, kullan\u0131c\u0131n\u0131n i\u015flemi kesmesine izin verir.<\/p>\n
5.  NFS sunucusunda rpc.mountd<\/code> veya rpcbind<\/code> hatalar\u0131:<\/strong>
\n    *   Neden:<\/strong> RPC servisleri d\u00fczg\u00fcn \u00e7al\u0131\u015fm\u0131yor.
\n    *   \u00c7\u00f6z\u00fcm:<\/strong>
\n        *   Servislerin durumunu kontrol edin: systemctl status rpcbind<\/code> ve systemctl status nfs-kernel-server<\/code>.
\n        *   Gerekirse yeniden ba\u015flat\u0131n: systemctl restart rpcbind<\/code> ve systemctl restart nfs-kernel-server<\/code>.<\/p>\n
Bu sorun giderme ad\u0131mlar\u0131, \u00e7o\u011fu NFS ba\u011flant\u0131 sorununu \u00e7\u00f6zmenize yard\u0131mc\u0131 olacakt\u0131r. Her zaman log dosyalar\u0131n\u0131 (\u00f6rne\u011fin \/var\/log\/syslog<\/code> veya dmesg<\/code>) kontrol etmek, sorunun k\u00f6kenini anlamak i\u00e7in de\u011ferli bilgiler sa\u011flayabilir.<\/p>\n
NFS G\u00fcvenli\u011fi \u0130\u00e7in En \u0130yi Uygulamalar<\/h3>\n
NFS, a\u011f \u00fczerinden dosya payla\u015f\u0131m\u0131 i\u00e7in g\u00fc\u00e7l\u00fc bir ara\u00e7 olsa da, \u00f6zellikle eski s\u00fcr\u00fcmleri (NFSv3) g\u00fcvenlik konusunda baz\u0131 zay\u0131fl\u0131klara sahiptir. Bu nedenle, NFS kurulumunuzu g\u00fcvence alt\u0131na almak i\u00e7in baz\u0131 en iyi uygulamalar\u0131 takip etmek hayati \u00f6nem ta\u015f\u0131r.<\/p>\n
1.  IP Tabanl\u0131 K\u0131s\u0131tlama:<\/strong>
\n       \/etc\/exports<\/code> dosyas\u0131nda <\/em><\/code> (t\u00fcm istemciler) yerine her zaman belirli IP adreslerini veya IP aral\u0131klar\u0131n\u0131 (CIDR notasyonu ile) kullan\u0131n. Bu, yaln\u0131zca yetkili istemcilerin payla\u015f\u0131ma eri\u015febilmesini sa\u011flar.
\n    *   \u00d6rnek: 192.168.1.101(rw,sync,no_subtree_check)<\/code> veya 192.168.1.0\/24(ro,sync,no_subtree_check)<\/code>.<\/p>\n
2.  G\u00fcvenlik Duvar\u0131 Kullan\u0131m\u0131 (UFW\/iptables):<\/strong>
\n    *   NFS sunucusunda, g\u00fcvenlik duvar\u0131n\u0131 (UFW veya iptables) kullanarak sadece belirli istemci IP’lerinden gelen NFS portlar\u0131na (2049, 111) eri\u015fime izin verin.
\n    *   Asla t\u00fcm a\u011fdan veya internetten NFS portlar\u0131n\u0131 a\u00e7may\u0131n.
\n    *   \u00d6rnek: sudo ufw allow from 192.168.1.101 to any port nfs<\/code>.<\/p>\n
3.  no_root_squash<\/code> Kullan\u0131m\u0131ndan Ka\u00e7\u0131nma:<\/strong>
\n    *   no_root_squash<\/code> se\u00e7ene\u011fi, istemcideki root<\/code> kullan\u0131c\u0131s\u0131n\u0131n sunucuda root<\/code> olarak i\u015flem yapmas\u0131na izin verir. Bu, istemci makinesinin g\u00fcvenli\u011fi ihlal edildi\u011finde sunucunun da kolayca ele ge\u00e7irilmesine yol a\u00e7abilir.
\n    *   M\u00fcmk\u00fcn oldu\u011funca root_squash<\/code> (varsay\u0131lan) veya all_squash<\/code> kullan\u0131n. Bu se\u00e7enekler, istemciden gelen root kullan\u0131c\u0131lar\u0131n\u0131n kimliklerini sunucudaki nobody<\/code> kullan\u0131c\u0131s\u0131na e\u015fleyerek ayr\u0131cal\u0131k y\u00fckseltme riskini azalt\u0131r.<\/p>\n
4.  Minimum Ayr\u0131cal\u0131k Prensibi:<\/strong>
\n    *   Payla\u015f\u0131mlar i\u00e7in her zaman en az ayr\u0131cal\u0131k ilkesini uygulay\u0131n. E\u011fer bir payla\u015f\u0131m sadece okunacaksa, \/etc\/exports<\/code> dosyas\u0131nda ro<\/code> (read-only) se\u00e7ene\u011fini kullan\u0131n.
\n    *   Payla\u015f\u0131lan dizinlerin dosya sistemi izinlerini (chmod<\/code>, chown<\/code>) dikkatlice ayarlay\u0131n. Gerekmedik\u00e7e 777<\/code> gibi geni\u015f izinler vermekten ka\u00e7\u0131n\u0131n. Belirli bir kullan\u0131c\u0131 veya grup i\u00e7in izinler tan\u0131mlay\u0131n ve bu kullan\u0131c\u0131\/grubun UID\/GID’sini istemci ve sunucu aras\u0131nda e\u015flemeye \u00e7al\u0131\u015f\u0131n.<\/p>\n
5.  NFSv4 Kullan\u0131m\u0131:<\/strong>
\n    *   NFSv4, NFSv3’e g\u00f6re \u00f6nemli g\u00fcvenlik geli\u015ftirmeleri sunar. Tek bir port (2049\/TCP) \u00fczerinden \u00e7al\u0131\u015f\u0131r ve Kerberos kimlik do\u011frulama ile g\u00fc\u00e7l\u00fc g\u00fcvenlik sa\u011flar.
\n    *   Ubuntu 16.04, NFSv4’\u00fc destekler. E\u011fer g\u00fcvenlik birincil \u00f6nceli\u011finizse ve Kerberos altyap\u0131n\u0131z varsa, NFSv4’\u00fc yap\u0131land\u0131rmay\u0131 d\u00fc\u015f\u00fcnebilirsiniz. Bu makale NFSv3’e odaklanm\u0131\u015f olsa da, NFSv4’e ge\u00e7i\u015f, \u00f6zellikle kurumsal ortamlarda \u015fiddetle tavsiye edilir.<\/p>\n
6.  Veri \u015eifreleme (VPN\/IPsec):<\/strong>
\n    *   NFSv3, a\u011f \u00fczerinden aktar\u0131lan verileri \u015fifrelemez. Hassas verileri payla\u015f\u0131yorsan\u0131z, NFS trafi\u011fini bir VPN (Virtual Private Network) t\u00fcneli veya IPsec (Internet Protocol Security) \u00fczerinden y\u00f6nlendirmeyi d\u00fc\u015f\u00fcn\u00fcn. Bu, verilerin a\u011fda dinlenmesini (eavesdropping) \u00f6nler.<\/p>\n
7.  Fiziksel G\u00fcvenlik:<\/strong>
\n    *   NFS sunucusunun fiziksel g\u00fcvenli\u011finin sa\u011fland\u0131\u011f\u0131ndan emin olun. Yetkisiz fiziksel eri\u015fim, t\u00fcm yaz\u0131l\u0131msal g\u00fcvenlik \u00f6nlemlerini etkisiz hale getirebilir.<\/p>\n
8.  S\u0131k\u0131 G\u00fcncelleme Politikas\u0131:<\/strong>
\n    *   Hem NFS sunucusunu hem de istemcilerini d\u00fczenli olarak g\u00fcncelleyin (sudo apt update && sudo apt upgrade<\/code>). Bu, bilinen g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131n kapat\u0131lmas\u0131n\u0131 sa\u011flar.<\/p>\n
Bu en iyi uygulamalar\u0131 takip ederek, NFS ortam\u0131n\u0131z\u0131n g\u00fcvenli\u011fini \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131rabilir ve potansiyel riskleri minimize edebilirsiniz. Unutmay\u0131n ki g\u00fcvenlik, s\u00fcrekli bir s\u00fcre\u00e7tir ve her zaman g\u00fcncel tehditlere kar\u015f\u0131 tetikte olmak gerekir.<\/p>\n
Sonu\u00e7<\/h3>\n
Bu kapsaml\u0131 rehberde, Ubuntu 16.04 \u00fczerinde bir NFS sunucusu kurma ve bir NFS istemcisini yap\u0131land\u0131rma s\u00fcre\u00e7lerini ad\u0131m ad\u0131m ele ald\u0131k. NFS’in ne oldu\u011fundan, neden kullan\u0131ld\u0131\u011f\u0131na, \u00f6n gereksinimlerden kurulum ve yap\u0131land\u0131rma ad\u0131mlar\u0131na, ba\u011flant\u0131 testlerinden sorun giderme y\u00f6ntemlerine ve son olarak g\u00fcvenlik i\u00e7in en iyi uygulamalara kadar bir\u00e7ok konuya de\u011findik.<\/p>\n
NFS, a\u011f \u00fczerinden dosya payla\u015f\u0131m\u0131 i\u00e7in g\u00fc\u00e7l\u00fc, esnek ve yayg\u0131n olarak kullan\u0131lan bir protokold\u00fcr. Merkezi bir depolama \u00e7\u00f6z\u00fcm\u00fc sunarak veri y\u00f6netimini basitle\u015ftirir, kaynak payla\u015f\u0131m\u0131n\u0131 kolayla\u015ft\u0131r\u0131r ve birden fazla sistemin ayn\u0131 verilere \u015feffaf bir \u015fekilde eri\u015fmesine olanak tan\u0131r. \u00d6zellikle Ubuntu 16.04 gibi LTS s\u00fcr\u00fcmlerinde, kararl\u0131 ve g\u00fcvenilir bir dosya payla\u015f\u0131m altyap\u0131s\u0131 sa\u011flamak i\u00e7in hala pop\u00fcler bir tercihtir.<\/p>\n
Kurulum s\u00fcrecinde, nfs-kernel-server<\/code> ve nfs-common<\/code> paketlerinin y\u00fcklenmesi, \/etc\/exports<\/code> dosyas\u0131n\u0131n do\u011fru bir \u015fekilde yap\u0131land\u0131r\u0131lmas\u0131 ve g\u00fcvenlik duvar\u0131 (UFW) kurallar\u0131n\u0131n ayarlanmas\u0131 kritik ad\u0131mlard\u0131r. \u0130stemci taraf\u0131nda ise, ba\u011flama noktas\u0131n\u0131n olu\u015fturulmas\u0131 ve \/etc\/fstab<\/code> arac\u0131l\u0131\u011f\u0131yla otomatik ba\u011flant\u0131n\u0131n sa\u011flanmas\u0131, sistemin kararl\u0131 ve s\u00fcrekli \u00e7al\u0131\u015fmas\u0131 i\u00e7in \u00f6nemlidir.<\/p>\n
G\u00fcvenlik, NFS kurulumunda g\u00f6z ard\u0131 edilmemesi gereken bir fakt\u00f6rd\u00fcr. IP tabanl\u0131 k\u0131s\u0131tlamalar, g\u00fcvenlik duvar\u0131 kurallar\u0131, no_root_squash<\/code> kullan\u0131m\u0131ndan ka\u00e7\u0131nma ve minimum ayr\u0131cal\u0131k prensibinin uygulanmas\u0131, NFS ortam\u0131n\u0131z\u0131 olas\u0131 tehditlere kar\u015f\u0131 korumak i\u00e7in temel ad\u0131mlard\u0131r. Hassas veriler i\u00e7in NFSv4’\u00fcn Kerberos kimlik do\u011frulamas\u0131 veya VPN\/IPsec t\u00fcnelleri arac\u0131l\u0131\u011f\u0131yla veri \u015fifrelemesi gibi daha geli\u015fmi\u015f g\u00fcvenlik \u00f6nlemlerini de\u011ferlendirmek, kurumlar i\u00e7in hayati \u00f6neme sahiptir.<\/p>\n
Umar\u0131z bu rehber, Ubuntu 16.04 sistemlerinizde NFS payla\u015f\u0131mlar\u0131n\u0131 ba\u015far\u0131l\u0131 bir \u015fekilde kurman\u0131z ve y\u00f6netmeniz i\u00e7in size sa\u011flam bir temel sunmu\u015ftur. Do\u011fru yap\u0131land\u0131rma ve g\u00fcvenlik uygulamalar\u0131yla, NFS, a\u011f altyap\u0131n\u0131z i\u00e7in de\u011ferli ve verimli bir bile\u015fen haline gelecektir. Gelecekte, daha modern NFS s\u00fcr\u00fcmlerini (NFSv4.1 veya \u00fcst\u00fc) veya alternatif da\u011f\u0131t\u0131k dosya sistemlerini (Ceph, GlusterFS) ke\u015ffederek depolama \u00e7\u00f6z\u00fcmlerinizi daha da optimize etmeyi d\u00fc\u015f\u00fcnebilirsiniz.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber\nGiri\u015f: NFS Nedir ve Neden Kullan\u0131l\u0131r?\nNFS (Network File System),","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1468],"tags":[],"class_list":{"0":"post-38936","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-ubuntu","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nUbuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber\" \/>\n<meta property=\"og:description\" content=\"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber Giri\u015f: NFS Nedir ve Neden Kullan\u0131l\u0131r? NFS (Network File System),\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-10T21:40:55+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"23 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber\",\"datePublished\":\"2026-02-10T21:40:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/\"},\"wordCount\":4005,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Ubuntu\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/\",\"name\":\"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-02-10T21:40:55+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/","og_locale":"tr_TR","og_type":"article","og_title":"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber","og_description":"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber Giri\u015f: NFS Nedir ve Neden Kullan\u0131l\u0131r? NFS (Network File System),","og_url":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-02-10T21:40:55+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"23 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber","datePublished":"2026-02-10T21:40:55+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/"},"wordCount":4005,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Ubuntu"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/","url":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/","name":"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-02-10T21:40:55+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/ubuntu-16-04-uzerinde-nfs-baglantisi-kurulumu-adim-adim-kapsamli-rehber\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Ubuntu 16.04 \u00dczerinde NFS Ba\u011flant\u0131s\u0131 Kurulumu: Ad\u0131m Ad\u0131m Kapsaml\u0131 Rehber"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/38936","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=38936"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/38936\/revisions"}],"predecessor-version":[{"id":38937,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/38936\/revisions\/38937"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=38936"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=38936"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=38936"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}