large data transfer to raid results in system reboot
Hello all,
I am having a problem transferring large amount of data to my hardware raid array. I am trying to copy ~32GB's of data from a mounted drive on another machine to a hardware raid0 array with an xfs filesystem. I've tried copying the data with both a "cp -a" and using ftp. Both methods result in the target system rebooting itself without any indication as to why in either dmesg or /var/log/messages. This problem started after the system in question rebooted and the xfs partition was corrupted. I recreated the raid array and everything is fine except for the reboot problem. I've run xfs_repair on the drive.
Some details:
System is FC4
[mythtv@divosbitch]/archive/music> uname -r
2.6.15-1.1833_FC4smp
[root@divosbitch ~]# /sbin/hdparm /dev/hda
/dev/hda:
multcount = 0 (off)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 48642/255/63, sectors = 400099246080, start = 0
[root@divosbitch ~]# fdisk -l
Disk /dev/hda: 400.0 GB, 400099246080 bytes
255 heads, 63 sectors/track, 48642 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 48642 390716833+ 83 Linux
Disk /dev/hde: 10.0 GB, 10005037056 bytes
255 heads, 63 sectors/track, 1216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hde1 * 1 13 104391 83 Linux
/dev/hde2 14 1216 9663097+ 8e Linux LVM
I was hoping that someone could give me some insight on how to begin to troubleshoot this problem as there are no errors reported in the logs... is there some sort of system monitor that I could install that would give me more clues on the cause for the reboot?
I thought initially that this could be a power supply problem, but when I initially built the system, I ran the copies just fine... also, the system was up for ~30 days before it went down.
Any suggestions are greatly appreciated.
Thanks,
Dave
|