• 05-06-2014, 00:02:00
    #1
    Bu sabah kalktığımda HDD nin full dolu olduğunu gördüm, gereksiz dosyaları sileyim derken en önemli siteleri uçurdum Allah'tan şirket haftalık yedek alıyormuş, soruma gelince yedek kurulduğunda HDD boyutu 33GB/40GB idi ancak 3-4 saatte 39Gb'a dayandı yine, bu neden kaynaklanıyor yeni üretilen dosyaların log'una nasıl ulaşırım? Cronjob çalıştırıyorum bunun etkisi olabilirmi? işin içinden çıkamıyorum
  • 05-06-2014, 02:59:39
    #2
    Kimlik doğrulama veya yönetimden onay bekliyor.
    Merhaba @shafack,

    du -h / | grep ^[5-9][0-9][0-9][0-9.]*M | sort

    komutunun çıktısını görebilir miyim?
  • 05-06-2014, 11:38:18
    #3
    Şu an siteler göçmüş vaziyette, sorunu çözebilirsem tekrar restore yapılmasını isteyeceğim.

    root@server1 [/]# du -h / | grep ^[5-9][0-9][0-9][0-9.]*M | sort
    du: cannot access `/proc/5664/task/5664/fd/4': No such file or directory
    du: cannot access `/proc/5664/task/5664/fdinfo/4': No such file or directory
    du: cannot access `/proc/5664/fd/4': No such file or directory
    du: cannot access `/proc/5664/fdinfo/4': No such file or directory
    du: cannot access `/home/virtfs/cancerli/proc/5664/task/5664/fd/4': No such file                                                                                                                                or directory
    du: cannot access `/home/virtfs/cancerli/proc/5664/task/5664/fdinfo/4': No such                                                                                                                                file or directory
    du: cannot access `/home/virtfs/cancerli/proc/5664/fd/4': No such file or direct                                                                                                                               ory
    du: cannot access `/home/virtfs/cancerli/proc/5664/fdinfo/4': No such file or di                                                                                                                               rectory
    du: cannot access `/home/virtfs/technolo/proc/5664/task/5664/fd/4': No such file                                                                                                                                or directory
    du: cannot access `/home/virtfs/technolo/proc/5664/task/5664/fdinfo/4': No such                                                                                                                                file or directory
    du: cannot access `/home/virtfs/technolo/proc/5664/fd/4': No such file or direct                                                                                                                               ory
    du: cannot access `/home/virtfs/technolo/proc/5664/fdinfo/4': No such file or di                                                                                                                               rectory
    du: cannot access `/home/virtfs/whichdis/proc/5664/task/5664/fd/4': No such file                                                                                                                                or directory
    du: cannot access `/home/virtfs/whichdis/proc/5664/task/5664/fdinfo/4': No such                                                                                                                                file or directory
    du: cannot access `/home/virtfs/whichdis/proc/5664/fd/4': No such file or direct                                                                                                                               ory
    du: cannot access `/home/virtfs/whichdis/proc/5664/fdinfo/4': No such file or di                                                                                                                               rectory
    du: cannot access `/home/virtfs/mynews/proc/5664/task/5664/fd/4': No such file o                                                                                                                               r directory
    du: cannot access `/home/virtfs/mynews/proc/5664/task/5664/fdinfo/4': No such fi                                                                                                                               le or directory
    du: cannot access `/home/virtfs/mynews/proc/5664/fd/4': No such file or director                                                                                                                               y
    du: cannot access `/home/virtfs/mynews/proc/5664/fdinfo/4': No such file or dire                                                                                                                               ctory
    du: cannot access `/home/virtfs/newandro/proc/5664/task/5664/fd/4': No such file or directory
    du: cannot access `/home/virtfs/newandro/proc/5664/task/5664/fdinfo/4': No such file or directory
    du: cannot access `/home/virtfs/newandro/proc/5664/fd/4': No such file or directory
    du: cannot access `/home/virtfs/newandro/proc/5664/fdinfo/4': No such file or directory
    501M    /root/ngx_pagespeed-1.7.30.1-beta
    533M    /home/virtfs/cancerli/usr/share
    533M    /home/virtfs/mynews/usr/share
    533M    /home/virtfs/newandro/usr/share
    533M    /home/virtfs/technolo/usr/share
    533M    /home/virtfs/whichdis/usr/share
    542M    /usr/share
    569M    /home/technolo/public_html/wp-content/uploads/2014
    569M    /home/virtfs/technolo/home/technolo/public_html/wp-content/uploads/2014
    641M    /root/ngx_pagespeed-release-1.6.29.5-beta
    645M    /home/virtfs/cancerli/usr/local/cpanel/bin
    645M    /home/virtfs/mynews/usr/local/cpanel/bin
    645M    /home/virtfs/newandro/usr/local/cpanel/bin
    645M    /home/virtfs/technolo/usr/local/cpanel/bin
    645M    /home/virtfs/whichdis/usr/local/cpanel/bin
    645M    /usr/local/cpanel/bin
    680M    /home/mynews/public_html/wp-content/uploads
    680M    /home/virtfs/mynews/home/mynews/public_html/wp-content/uploads
    822M    /home/technolo/public_html/wp-content/uploads
    822M    /home/virtfs/technolo/home/technolo/public_html/wp-content/uploads
    844M    /home/technolo/public_html/wp-content
    844M    /home/virtfs/technolo/home/technolo/public_html/wp-content
    862M    /home/technolo/public_html
    862M    /home/virtfs/technolo/home/technolo/public_html
    901M    /home/mynews/public_html/wp-content
    901M    /home/virtfs/mynews/home/mynews/public_html/wp-content
    917M    /home/mynews/public_html
    917M    /home/virtfs/mynews/home/mynews/public_html
    root@server1 [/]#
  • 05-06-2014, 11:51:08
    #4
    Tüm hesaplar için Jailed shell çevresel birimini umount ederek başlayabilirsin.

    Örnek veriyorum;

    umount /home/virtfs/cancerli/usr/local/cpanel/bin
    umount /home/virtfs/mynews/usr/local/cpanel/bin
    umount /home/virtfs/newandro/usr/local/cpanel/bin
    umount /home/virtfs/technolo/usr/local/cpanel/bin
    umount /home/virtfs/whichdis/usr/local/cpanel/bin

    gibi...

    Daha sonra df -h ile ne kadar alan kaldığını doğrulayın.
  • 05-06-2014, 13:26:28
    #5
    umount ne işe yarar? (öğrenmek için soruyorum), şu an test etmek için

    umount /home/virtfs/cancerli/usr/local/cpanel/bin
    komutunu kullandığımda

    error writing /etc/mtab.tmp: Disk quota exceeded
    umount: /home/virtfs/cancerli/usr/local/cpanel/bin: not mounted
    hatası veriyor

    eğer adamlardan 2 gün önceki yedeği tekrar kurmalarını istesem ve bu komutları tek tek uygulasam sorunum çözülmüş olurmu?

    Otomatik veri çeken cronjoblarım var, sanırım onlardan kaynaklanıyor sorun gerekirse onuda iptal ederim

    AndyCap adlı üyeden alıntı: mesajı görüntüle
    Tüm hesaplar için Jailed shell çevresel birimini umount ederek başlayabilirsin.

    Örnek veriyorum;

    umount /home/virtfs/cancerli/usr/local/cpanel/bin
    umount /home/virtfs/mynews/usr/local/cpanel/bin
    umount /home/virtfs/newandro/usr/local/cpanel/bin
    umount /home/virtfs/technolo/usr/local/cpanel/bin
    umount /home/virtfs/whichdis/usr/local/cpanel/bin

    gibi...

    Daha sonra df -h ile ne kadar alan kaldığını doğrulayın.
  • 05-06-2014, 18:20:57
    #6
    @shafack,

    grep -i 'cancerli' /proc/mounts çıktısı nedir?
  • 05-06-2014, 19:35:49
    #7
    AndyCap adlı üyeden alıntı: mesajı görüntüle
    @shafack,

    grep -i 'cancerli' /proc/mounts çıktısı nedir?
    Boş dönüyor hocam yalnız az önce 3 gün önceye aldırdım makineyi
  • 05-06-2014, 19:39:02
    #8
    shafack adlı üyeden alıntı: mesajı görüntüle
    Boş dönüyor hocam yalnız az önce 3 gün önceye aldırdım makineyi
    Boş dönüyor ise, bağlı olmadıklarını gösteriyor ve o alanları silmemen için bir sebep gözükmüyor.

    645M /home/virtfs/cancerli/usr/local/cpanel/bin
    645M /home/virtfs/mynews/usr/local/cpanel/bin
    645M /home/virtfs/newandro/usr/local/cpanel/bin
    645M /home/virtfs/technolo/usr/local/cpanel/bin
    645M /home/virtfs/whichdis/usr/local/cpanel/bin


    Şu alanları rm -rf /home/virtfs/cancerli/usr/local/cpanel/bin ile silebilirsiniz örneğin.
  • 05-06-2014, 20:06:14
    #9
    yukarıda ki grep komutunu mynews kullanıcı kodlu site için uyguladığımda
    /dev/simfs /home/virtfs/mynews/lib simfs ro,nosuid,relatime 0 0
    /dev/simfs /home/virtfs/mynews/bin simfs ro,nosuid,relatime 0 0
    /dev/simfs /home/virtfs/mynews/sbin simfs ro,nosuid,relatime 0 0
    /dev/simfs /home/virtfs/mynews/opt simfs ro,nosuid,relatime 0 0
    /dev/simfs /home/virtfs/mynews/lib64 simfs ro,nosuid,relatime 0 0
    /dev/simfs /home/virtfs/mynews/usr simfs ro,nosuid,relatime 0 0
    /dev/simfs /home/virtfs/mynews/var simfs ro,nosuid,relatime 0 0
    /dev/simfs /home/virtfs/mynews/var/spool simfs rw,nosuid,noexec,relatime 0 0
    /dev/simfs /home/virtfs/mynews/var/log simfs rw,nosuid,noexec,relatime 0 0
    /dev/simfs /home/virtfs/mynews/etc/mail simfs rw,nosuid,noexec,relatime 0 0
    /dev/simfs /home/virtfs/mynews/tmp simfs rw,nosuid,noexec,relatime 0 0
    /dev/simfs /home/virtfs/mynews/var/tmp simfs rw,nosuid,noexec,relatime 0 0
    none /home/virtfs/mynews/dev devtmpfs rw,nosuid,noexec,relatime,mode=755 0 0
    /dev/simfs /home/virtfs/mynews/usr/sbin simfs ro,relatime 0 0
    /dev/simfs /home/virtfs/mynews/home/mynews simfs rw,relatime 0 0
    none /home/virtfs/mynews/proc proc rw,relatime 0 0
    çıktısı verdi, bunları silemiyorum herhalde

    nginx log access log error log bunları nasıl kaparız peki?