disk problemi - R10.net

05-01-2017, 21:01:29

arkadaşlar merhaba, konu daha hızlı görülür düşüncesiyle buraya açmak durumunda kaldım.

vmware üzerinde yapılandırdığımız bir sunucu var. sunucu bugün bir anda disk kullanımını %100'e getirdi. bir kaç yedek sildik,yeniden başlattık. ardından tekrar disk dolmaya başladı.

şu anki vaziyeti budur.

Ortada tahmini olarak 150 gb civarı bir şişme durumu var.

kök dizini dahil bir çok yeri tarayarak kontrol ettik fakat göze çarpan büyüklükte bir dosyaya rastlayamadık. fsck ile disk onarmayı düşündük acaba kendini toplar mı diye, henüz bu işlemi de yapmadık. bu tarz bir durumla karşılaşan veya fikri olan var mıdır?

sevgiler.

05-01-2017, 21:14:05

#2

~~Erebus~~

Aynı şekilde loglarda inceleme yapmak gerekiyor.

05-01-2017, 21:15:38

#3

hknm

/var/log şişmiştir büyük ihtimalle.

05-01-2017, 21:20:55

#4

hasantokaloglu

hknm adlı üyeden alıntı: mesajı görüntüle

/var/log şişmiştir büyük ihtimalle.

kontrol ettik hocam orayı bir şişme durumuna rastlamadık.

Alıntı

0 anaconda
673M apache2
2.1M apf_log
1.7M apf_log-20161226
1.8M apf_log-20170101
38M audit
4.0K bfd_log
4.0K bfd_log-20161226
4.0K bfd_log-20170101
12K boot.log
4.0K btmp
64M chkservd.log
88K clam-update.log
3.9M cron
240K cron-20161226
4.7M cron-20170101
844K dcpumon
108K dmesg
108K dmesg.old
29M exim_mainlog
5.3M exim_mainlog-20161226.gz
5.7M exim_mainlog-20170101.gz
4.0K exim_paniclog
4.0K exim_paniclog-20170101.gz
100K exim_rejectlog
20K exim_rejectlog-20161226.gz
100K exim_rejectlog-20170101.gz
4.0K fail2ban.log
4.0K fail2ban.log-20161226
4.0K fail2ban.log-20170101
48K lastlog
14M maillog
580K maillog-20161226
17M maillog-20170101
11M messages
1.1M messages-20161226
12M messages-20170101
91M munin
0 named
0 ppp
22M sa
24K secure
4.0K secure-20161226
16K secure-20170101
0 spooler
0 spooler-20170101
52K tuned
884K uptrack.log
2.6M uptrack.log.1
5.1M vmware-vmsvc.1.log
1.9M vmware-vmsvc.log
96K wtmp
4.0K xferlog.offset
4.0K xferlog.offsetftpsep
4.0K yum.log
128K yum.log-20170101

05-01-2017, 21:26:08

#5

hknm

Cpanel mi bu sanal sunucu? /home dizinini kontrol edin bir de. Bir yerlerde olmalı saklanmış olamaz.

05-01-2017, 21:33:15

#6

hasantokaloglu

Erebus adlı üyeden alıntı: mesajı görüntüle

Aynı şekilde loglarda inceleme yapmak gerekiyor.

du -ch /vmimages /var/core /root /var/log çıktısı hocam. anormallik yok gibi

du: cannot access ‘/vmimages’: No such file or directory
du: cannot access ‘/var/core’: No such file or directory
12K /root/.gnupg
8.0K /root/.HttpRequest
252K /root/.MirrorSearch/httpupdate.cpanel.net/pingtimes
256K /root/.MirrorSearch/httpupdate.cpanel.net
24K /root/.MirrorSearch/cabundle.cpanel.net/pingtimes
28K /root/.MirrorSearch/cabundle.cpanel.net
284K /root/.MirrorSearch
2.2M /root/.spamassassin/sa-compile.cache
2.2M /root/.spamassassin
640K /root/.cpanel/datastore
944K /root/.cpanel/caches/dynamicui
944K /root/.cpanel/caches
0 /root/.cpanel/comet/root/subscriptions
4.0K /root/.cpanel/comet/root/channels/%2fremove_messages_mail_queue%2f0BR33SNqz65_XC8L/feed
708K /root/.cpanel/comet/root/channels/%2fremove_messages_mail_queue%2f0BR33SNqz65_XC8L/messages
712K /root/.cpanel/comet/root/channels/%2fremove_messages_mail_queue%2f0BR33SNqz65_XC8L
4.0K /root/.cpanel/comet/root/channels/%2fremove_messages_mail_queue%2f0Sm8RuX88kU2QYBw/feed
708K /root/.cpanel/comet/root/channels/%2fremove_messages_mail_queue%2f0Sm8RuX88kU2QYBw/messages
712K /root/.cpanel/comet/root/channels/%2fremove_messages_mail_queue%2f0Sm8RuX88kU2QYBw
4.0K /root/.cpanel/comet/root/channels/%2fremove_messages_mail_queue%2fMx9VbgMkz8HndVaV/feed
568K /root/.cpanel/comet/root/channels/%2fremove_messages_mail_queue%2fMx9VbgMkz8HndVaV/messages
572K /root/.cpanel/comet/root/channels/%2fremove_messages_mail_queue%2fMx9VbgMkz8HndVaV
2.0M /root/.cpanel/comet/root/channels
0 /root/.cpanel/comet/root/subscriber_channel_positions
2.0M /root/.cpanel/comet/root
2.0M /root/.cpanel/comet
3.6M /root/.cpanel
4.0K /root/tmp/pear
4.0K /root/tmp
0 /root/perl5
0 /root/.pki/nssdb
0 /root/.pki
4.4M /root/.razor
8.0K /root/.cache/pip/http/a/6/9/b/d
8.0K /root/.cache/pip/http/a/6/9/b
8.0K /root/.cache/pip/http/a/6/9
8.0K /root/.cache/pip/http/a/6
68K /root/.cache/pip/http/a/e/0/0/7
68K /root/.cache/pip/http/a/e/0/0
68K /root/.cache/pip/http/a/e/0
68K /root/.cache/pip/http/a/e
840K /root/.cache/pip/http/a/4/1/3/6
840K /root/.cache/pip/http/a/4/1/3
840K /root/.cache/pip/http/a/4/1
840K /root/.cache/pip/http/a/4
52K /root/.cache/pip/http/a/5/5/9/a
52K /root/.cache/pip/http/a/5/5/9
52K /root/.cache/pip/http/a/5/5
52K /root/.cache/pip/http/a/5
968K /root/.cache/pip/http/a
1.2M /root/.cache/pip/http/8/e/9/7/a
1.2M /root/.cache/pip/http/8/e/9/7
1.2M /root/.cache/pip/http/8/e/9
1.2M /root/.cache/pip/http/8/e
4.0K /root/.cache/pip/http/8/f/5/5/e
4.0K /root/.cache/pip/http/8/f/5/5
4.0K /root/.cache/pip/http/8/f/5
4.0K /root/.cache/pip/http/8/f
4.0K /root/.cache/pip/http/8/d/e/d/a
4.0K /root/.cache/pip/http/8/d/e/d
4.0K /root/.cache/pip/http/8/d/e
4.0K /root/.cache/pip/http/8/d
1.2M /root/.cache/pip/http/8
8.0K /root/.cache/pip/http/d/9/f/5/0
8.0K /root/.cache/pip/http/d/9/f/5
8.0K /root/.cache/pip/http/d/9/f
8.0K /root/.cache/pip/http/d/9
8.0K /root/.cache/pip/http/d/e/f/7/0
8.0K /root/.cache/pip/http/d/e/f/7
8.0K /root/.cache/pip/http/d/e/f
8.0K /root/.cache/pip/http/d/e
16K /root/.cache/pip/http/d
24K /root/.cache/pip/http/f/e/d/0/e
24K /root/.cache/pip/http/f/e/d/0
24K /root/.cache/pip/http/f/e/d
24K /root/.cache/pip/http/f/e
16K /root/.cache/pip/http/f/1/7/c/6
16K /root/.cache/pip/http/f/1/7/c
16K /root/.cache/pip/http/f/1/7
16K /root/.cache/pip/http/f/1
40K /root/.cache/pip/http/f
28K /root/.cache/pip/http/7/f/9/4/c
28K /root/.cache/pip/http/7/f/9/4
28K /root/.cache/pip/http/7/f/9
28K /root/.cache/pip/http/7/f
2.4M /root/.cache/pip/http/7/0/3/0/c
2.4M /root/.cache/pip/http/7/0/3/0
2.4M /root/.cache/pip/http/7/0/3
2.4M /root/.cache/pip/http/7/0
4.0K /root/.cache/pip/http/7/b/a/7/8
4.0K /root/.cache/pip/http/7/b/a/7
4.0K /root/.cache/pip/http/7/b/a
4.0K /root/.cache/pip/http/7/b
24K /root/.cache/pip/http/7/7/f/b/3
24K /root/.cache/pip/http/7/7/f/b
24K /root/.cache/pip/http/7/7/f
24K /root/.cache/pip/http/7/7
12K /root/.cache/pip/http/7/4/3/9/b
12K /root/.cache/pip/http/7/4/3/9
12K /root/.cache/pip/http/7/4/3
12K /root/.cache/pip/http/7/4
2.5M /root/.cache/pip/http/7
8.0K /root/.cache/pip/http/9/4/b/1/1
8.0K /root/.cache/pip/http/9/4/b/1
8.0K /root/.cache/pip/http/9/4/b
8.0K /root/.cache/pip/http/9/4
8.0K /root/.cache/pip/http/9
20K /root/.cache/pip/http/c/7/c/1/9
20K /root/.cache/pip/http/c/7/c/1
20K /root/.cache/pip/http/c/7/c
20K /root/.cache/pip/http/c/7
4.0K /root/.cache/pip/http/c/f/1/7/1
4.0K /root/.cache/pip/http/c/f/1/7
4.0K /root/.cache/pip/http/c/f/1
4.0K /root/.cache/pip/http/c/f
24K /root/.cache/pip/http/c
4.0K /root/.cache/pip/http/5/9/7/1/d
4.0K /root/.cache/pip/http/5/9/7/1
4.0K /root/.cache/pip/http/5/9/7
4.0K /root/.cache/pip/http/5/9
4.0K /root/.cache/pip/http/5
28K /root/.cache/pip/http/4/8/1/e/9
28K /root/.cache/pip/http/4/8/1/e
28K /root/.cache/pip/http/4/8/1
28K /root/.cache/pip/http/4/8
1.6M /root/.cache/pip/http/4/1/b/f/0
1.6M /root/.cache/pip/http/4/1/b/f
1.6M /root/.cache/pip/http/4/1/b
1.6M /root/.cache/pip/http/4/1
36K /root/.cache/pip/http/4/4/3/a/8
36K /root/.cache/pip/http/4/4/3/a
36K /root/.cache/pip/http/4/4/3
36K /root/.cache/pip/http/4/4
1.7M /root/.cache/pip/http/4
48K /root/.cache/pip/http/e/b/0/4/2
48K /root/.cache/pip/http/e/b/0/4
48K /root/.cache/pip/http/e/b/0
48K /root/.cache/pip/http/e/b
200K /root/.cache/pip/http/e/2/b/7/4
200K /root/.cache/pip/http/e/2/b/7
200K /root/.cache/pip/http/e/2/b
200K /root/.cache/pip/http/e/2
248K /root/.cache/pip/http/e
4.0K /root/.cache/pip/http/b/9/2/d/5
4.0K /root/.cache/pip/http/b/9/2/d
4.0K /root/.cache/pip/http/b/9/2
4.0K /root/.cache/pip/http/b/9
4.0K /root/.cache/pip/http/b
12K /root/.cache/pip/http/0/7/7/a/f
12K /root/.cache/pip/http/0/7/7/a
12K /root/.cache/pip/http/0/7/7
12K /root/.cache/pip/http/0/7
12K /root/.cache/pip/http/0
6.5M /root/.cache/pip/http
500K /root/.cache/pip/wheels/db/de/bd/b99b1e12d321fbc950766c58894c6576b1a73ae3131b29a151
500K /root/.cache/pip/wheels/db/de/bd
500K /root/.cache/pip/wheels/db/de
500K /root/.cache/pip/wheels/db
500K /root/.cache/pip/wheels
7.0M /root/.cache/pip
7.0M /root/.cache
8.0K /root/.aws
0 /root/cpanel3-skel/public_html
0 /root/cpanel3-skel/public_ftp
0 /root/cpanel3-skel
4.0K /root/.ssh
0 /root/.libnet-openssh-perl
0 /root/.config/htop
0 /root/.config
53M /root
0 /var/log/ppp
52K /var/log/tuned
38M /var/log/audit
0 /var/log/anaconda
22M /var/log/sa
0 /var/log/named
226M /var/log/apache2/domlogs
0 /var/log/apache2/modsec_audit
135M /var/log/apache2/archive
685M /var/log/apache2
0 /var/log/dcpumon/2016/Aug
0 /var/log/dcpumon/2016/Sep
0 /var/log/dcpumon/2016/Oct
0 /var/log/dcpumon/2016/Nov
88K /var/log/dcpumon/2016/Dec
88K /var/log/dcpumon/2016
60K /var/log/dcpumon/boot.1482687001
16K /var/log/dcpumon/boot.1482687602
24K /var/log/dcpumon/boot.1482688502
36K /var/log/dcpumon/boot.1483641601
40K /var/log/dcpumon/2017/Jan
40K /var/log/dcpumon/2017
104K /var/log/dcpumon/boot.1483608901
8.0K /var/log/dcpumon/boot.1483609201
16K /var/log/dcpumon/boot.1483609501
8.0K /var/log/dcpumon/boot.1483609801
8.0K /var/log/dcpumon/boot.1483610102
16K /var/log/dcpumon/boot.1483610701
8.0K /var/log/dcpumon/boot.1483611002
60K /var/log/dcpumon/boot.1483638901
8.0K /var/log/dcpumon/boot.1483639201
8.0K /var/log/dcpumon/boot.1483639501
24K /var/log/dcpumon/boot.1483640401
36K /var/log/dcpumon/boot.1483642802
896K /var/log/dcpumon
90M /var/log/munin
1014M /var/log
1.1G total

hknm adlı üyeden alıntı: mesajı görüntüle

Cpanel mi bu sanal sunucu? /home dizinini kontrol edin bir de. Bir yerlerde olmalı saklanmış olamaz.

cpanel sunucu. home 90gb. çıldırttı

05-01-2017, 21:36:27

#7

Niroven

hasantokaloglu adlı üyeden alıntı: mesajı görüntüle

arkadaşlar merhaba, konu daha hızlı görülür düşüncesiyle buraya açmak durumunda kaldım.

vmware üzerinde yapılandırdığımız bir sunucu var. sunucu bugün bir anda disk kullanımını %100'e getirdi. bir kaç yedek sildik,yeniden başlattık. ardından tekrar disk dolmaya başladı.

şu anki vaziyeti budur.

Ortada tahmini olarak 150 gb civarı bir şişme durumu var.

kök dizini dahil bir çok yeri tarayarak kontrol ettik fakat göze çarpan büyüklükte bir dosyaya rastlayamadık. fsck ile disk onarmayı düşündük acaba kendini toplar mı diye, henüz bu işlemi de yapmadık. bu tarz bir durumla karşılaşan veya fikri olan var mıdır?

sevgiler.

CentOS sürümünüz eski mi?

05-01-2017, 21:41:09

#8

hasantokaloglu

Axerhosting adlı üyeden alıntı: mesajı görüntüle

CentOS sürümünüz eski mi?

Centos 7

05-01-2017, 21:43:37

#9

gangan

ssh bilgilerini pm atarsanız bir inceleyeyim