Strange behavior with simple backup routine
Hey all, I've created a simple backup system for quick restoring of files in case they get accidentally deleted. My backup server is running Debian Squeeze, and the storage is a 2TB MDADM RAID 10 array. I did something like this a while back and everything was working fine but I came in this morning and my Nagios server was complaining about my backup server (Critical CPU Usage and excessive processes). Here's what I'm using for my backup script:
Code:
mount -t cifs -o username=admin,password=Pass1! //192.168.2.29/Shares /mnt/Windows Code:
root 14684 0.0 0.0 45556 776 ? S 01:56 0:00 /USR/SBIN/CRON I started this from crontab (a different backup file for each day of the week) so I'm going to go in and kill that until I figure out what I'm doing wrong. Any help would be greatly appreciated. Thanks, Joe B |
The process status is your big indicator here that its a wait issue.
The process status of D is disk wait basically. Man page: Code:
D uninterruptible sleep (usually IO) |
Ok, thought it was because I was backing up over a 100Mb (when I thought it was a 1Gb connection) but that's not it. I'm running at 1Gb now and I'm still getting this error...
That was yesterday before I was interrupted. Today the server is almost unresponsive; ls -l takes about 10 seconds to display and an additional 10 seconds or so to run. I don't understand why this worked on another server a few months ago but not now. I'll kill this backup, create some wimpy folders and files and experiment on them while running Wireshark to see if I can figure this out. Thanks, Joe B |
All times are GMT -5. The time now is 07:29 AM. |