Run these commands

smartctl -a /dev/sda
smartctl -a /dev/sdb

If the value for Current_Pending_Sector is higher than 0 then you have some bad sectors.

If the value is quite low you could use hdrepair to repair the sectors.

Bir kac gundur bu sistemle ugrasiyordum.

2 Monitor (Dell U2412M – 24″ IPS ekran ) + 1 Adet HD Ready LG 32″ TV

Hedef 3 unu extend ederek sistemi olusturmakti.

Sahip oldugum NVIDIA MSI GTX560TI TwinFrozer II OC edition kartimda NVIDIA nin kisitlamalari nedeni ile bunu yapamayinca ( NVIDIA tek GPU ile ayni anda sadece 2 cihaz calistirabilirsin diyor)

Kartimi AMD tarafinda Sapphire HD6950 2GB bir kart ile Takas etmek yoluna gittim

6950 Default ayarlarinda GTX560 TI kartimdan aziciak daha iyi sonuclar veren denk bir kart.

Yeni AMD kart geldikten sonra su konfigurasyon ile islemi tamamladim

Monitor 1 Mini Display Port ile karttan cikiyor Kartin kutusundan cikan adaptor ile normal Display Port oluyor ve baglaniyor

Monitor 2 Standart DVI kablosu ile Kartin DVI cikislarinin ust tarafindakine takili

TV Standart HDMI olarak bagli

Sonuc her 3 monitordu de extend edebiliyorum su an

Bir yanda Tv + 2 Monitor

Guzel ve arzu ettigim bir setup oldu 🙂

NOT: 6950 Geldikten sonra bu kartin cok basit bir BIOS upgradei ile 6970 Olarak calistirilabildiginide farkettim.

Gerekli bilgi asagidaki linklerde var:

Bana Daha cok hiz veya 6970 Lazim olmadigindan su an islemi yapmiyorum. Ama belki ilerde yaparim bende 6950@6970 olayini.

http://www.techpowerup.com/articles/overclocking/vidcard/159

http://www.legitreviews.com/article/1608/5/

http://blog.daum.net/victorys/11153513

1- sistem geri yuklemeyi kapat

2- sanal bellek kapat > bilgisayar > ozellikler > gelismis sistem ayarlari > gelismis sekmesi > performans > ayarlar > sanal bellek

3- trim kontrol

cmd > fsutil behavior query disabledeletenotify

DisableDeleteNotify = 0 TRIM Aktif demektir.
DisableDeleteNotify = 1 TRIM Kapalı demektir.

4- ssdye ozellikler > indexing servisi kapat

original post: http://www.aip.im/2010/08/monitoring-proxmox-openvz-containers-bandwidth/

Monitoring Proxmox OpenVZ container’s bandwidth

Use these scripts to collect bandwidth data for each container. You can view the data on a graph and total usage by months.

The scripts are originally received from Hutzoft but modified to work with the Proxmox directory structure.

1. Install rrdtool and PHP support

apt-get install rrdtool php5

2. Download the bandwidth collection script and Web UI

wget http://www.aip.im/downloads/vzmonitor.tar.gz
or
wget http://www.shukko.com/vzmonitor.tar.gz

3. Unpack and relocate

tar zxvf vzmonitor.tar.gz
mkdir /usr/local/bandwidth
mv bandwidth.sh /usr/local/bandwidth/
chmod +x /usr/local/bandwidth/bandwidth.sh
mv vzmonitor /var/www/

4. Create a cron job to collect the data every 5 minutes (crontab -e)

*/5 * * * * cd /usr/local/bandwidth;./bandwidth.sh &> /dev/null

5. Add config to Apache (pico /etc/apache2/conf.d/vzmonitor.conf)

Alias /vzmonitor /var/www/vzmonitor

<Directory /var/www/vzmonitor>
DirectoryIndex index.php
</Directory>

6. Restart Apache

/etc/init.d/apache2 restart

7. It’s ready, wait a few minutes and enter this location to view the bandwidth usage: http://yourserver/vzmonitor

http://monalisa.cern.ch/FDT/

FDT is an Application for Efficient Data Transfers which is capable of reading and writing at disk speed over wide area networks (with standard TCP). It is written in Java, runs an all major platforms and it is easy to use.

FDT is based on an asynchronous, flexible multithreaded system and is using the capabilities of the Java NIO libraries. Its main features are:

• Streams a dataset (list of files) continuously, using a managed pool of buffers through one or more TCP sockets.
• Uses independent threads to read and write on each physical device
• Transfers data in parallel on multiple TCP streams, when necessary
• Uses appropriate-sized buffers for disk I/O and for the network
• Restores the files from buffers asynchronously
• Resumes a file transfer session without loss, when needed

FDT can be used to stream a large set of files across the network, so that a large dataset composed of thousands of files can be sent or received at full speed, without the network transfer restarting between files.

yum install setuptool
yum install system-config-network*
yum install system-config-securitylevel-tui
yum install ntsysv

yum install setuptool system-config-network* system-config-securitylevel-tui ntsysv

Original: http://www.buildingcubes.com/2012/07/25/installing-my-3tb-hard-drive-on-debian-linux-step-by-step/

You can format it EXT4, but ext2 and ext3 are also OK ! ext2 and ext3 allow up to 16TB disks, and file sizes of up to 2TB, ext4 allows much more.

Any linux kernel newer than 2.6.31 should work just fine with “Advanced format” drives using the exact same steps in this article.

MBR only supports 2TB drives, you need GPT, so let us get started

1- apt-get update
2- apt get install parted
3- parted /dev/sdc
4- mklabel gpt
5- Answer yes to: Warning: The existing disk label on /dev/sdb will be destroyed and all data on this disk will be lost. Do you want to continue?
Yes/No? yes
6- mkpart primary ext4 0% 100% (to make a partition as big as the disk (will occupy starting from first megabyte (for alignment) to the end of disk))
7- quit

Now to formating the drive

mkfs.ext4 /dev/sdc1

And there we are, Now we need to mount it at boot time by adding it to fstab, to do that, we will need the disk’s unique ID !

8- Now executing the following command will give you the unique ID of this new partition for use with fstab (The disk list we will edit below in step 10)
blkid /dev/sdc1
9- create the directory where you want to mount your hard disk, for example
mkdir /hds
mkdir /hds/3tb
10- Now, we add the following line to fstab

UUID=b7a491b1-a690-468f-882f-fbb4ac0a3b53       /hds/3tb            ext2     defaults,noatime                0       1

11- Now execute
mount -a

You are done,. if you execute
df -h
You should see your 2+TB hard drive in there !

orjinal link: http://www.debian-administration.org/articles/390

One common server bottleneck is DNS lookups. Many common server tasks such as from looking up hostnames to write Apache logfiles and processing incoming mail require the use of DNS queries. If you’re running a high-traffic system it might be useful to cache previous lookups.

There are several different packages you can use for caching DNS requests – including bind, djbdns, dnsmasq and pdnsd.

The pdnsd package is a very simple and lightweight tool for DNS caching. It will, like many of the other systems, act as a small DNS server forwarding requests to a “real” DNS server and caching the responses.

When pdnsd is stopped it will save all the lookups which have been made against it so they may be reloaded when it starts again.

Installation is very straightforward:

apt-get install pdnsd

Once installed the software is configured via the file /etc/pdnsd.conf.

To configure the software you must do two things:

• Configure pdnsd so that it will forward requests it doesn’t know about to a real DNS server, letting it cache those results.
• Update your system so that DNS lookups against the newly installed cache, or proxy.

Once you’ve completed these two steps all DNS lookups upon your system will be cached, and your DNS lookups should be much faster.

Upon your Debian GNU/Linux system you configure the DNS server(s) which are being used by means of the file, /etc/resolv.conf, this file will contain a list of name servers to query, perhaps along with a search domain to be used for unqualified hosts.

To tell your server to make DNS queries against the freshly installed server you would update that file to read:

nameserver 127.0.0.1

The next thing to do is to edit the pdnsd configuration file /etc/pdnsd.conf to specify which DNS servers the cache should use for its own lookups – these will most likely be your ISPs nameservers.

Locate the section of the configuration file which starts with server and add the IP address:

#
#  Specify the IP address of the real DNS server to query against here:
#
server {
        ip=11.22.33.44;   
        timeout=30;
        interval=30;
        uptest=ping;
        ping_timeout=50;
        purge_cache=off;
}

With this setting updated you can restart the caching service:

root@itchy:/etc# /etc/init.d/pdnsd restart
Restarting proxy DNS server: pdnsd.
root@itchy:/etc#

If you wish to add more DNS servers to query against you can add them seperated by commas, or you can add multiple ip= lines such as these two examples:

       # Several IPs seperated by commas.
       ip=11.22.33.44,111.222.333.444;

       # Easier to read - one per line:
       ip=11.22.33.44;
       ip=111.222.333.444;

For more details of the supported options please consult the documentation by running “man pdnsd.conf“.

You can test the cache is working by issuing a manual request to it:

root@itchy:/etc# dig  @localhost example.com mx

;; QUESTION SECTION:
;example.com.                   IN      MX

;; AUTHORITY SECTION:
example.com.            86400   IN      SOA     dns1.icann.org. hostmaster.icann.org.

;; Query time: 2224 msec
;; SERVER: 192.168.1.50#53(192.168.1.50)
;; WHEN: Sun Apr 23 21:47:41 2006
;; MSG SIZE  rcvd: 90

Here we used the dig command (part of the dnsutils package) to lookup the MX record of the domain name example.com. Notice at the bottom it shows “Query time: 2224msec”? Lets run that same query again – if our cache is working correctly it should be significantly faster:

root@itchy:/etc# dig  @itchy example.com mx |grep time
;; Query time: 1 msec

Much faster 🙂

(Yes DNS queries are ordinarily cached to a certain extent; so you’d expect the speedup even without our explicit DNS caching server…)

bir tane dizinim var
icinde 400.000 tane minik dosyam var
180 gunden eski olanlarini silmek istiyorum
argument list too long diyor klasik yontemler…
komutum nedir ?
Budur:

find . -type f -print -mtime +180 -delete



#!/bin/bash
for i in $( ls /var/cpanel/users ); do
/scripts/pkgacct $i /backup/cpbackup/daily backup nocompress
done