So, I made a thread a week or so ago with some conflicting issues.
I'm using FreeNAS 8.0.3p1 on a 1.3ghz Athlon with 512mb of memory.
I setup a raid 3 array using 2x200Gb and 1x160Gb drives using UFS.
I have the array shared over CIFS
I'm using Windows Backup in W7
In windows I setup windows backup to backup to the CIFS share. It starts backing up and about five minutes into the transfer dialogue it causes FreeNAS to lockup, drop a disk from the array, and reboot. It then started to rebuild the array. This was on a older 667Mhz Celeron with 384Mb of memory. After running into this multiple times I replaced the hardware including the PSU and upgraded from a raid 1 UFS array to a raid 3 UFS array.
It currently still does this now. The drive it drops seems to be ada3, but after shuffling the drives around a couple times, the drive it drops seems to be completely random. Furthermore trying to stress test it I've done multiple simultaneous copies to the computer through windows and it's rock solid for hours on end. It only seems to exhibit this behavior when trying to use windows backup.
I'm using FreeNAS 8.0.3p1 on a 1.3ghz Athlon with 512mb of memory.
I setup a raid 3 array using 2x200Gb and 1x160Gb drives using UFS.
I have the array shared over CIFS
I'm using Windows Backup in W7
In windows I setup windows backup to backup to the CIFS share. It starts backing up and about five minutes into the transfer dialogue it causes FreeNAS to lockup, drop a disk from the array, and reboot. It then started to rebuild the array. This was on a older 667Mhz Celeron with 384Mb of memory. After running into this multiple times I replaced the hardware including the PSU and upgraded from a raid 1 UFS array to a raid 3 UFS array.
It currently still does this now. The drive it drops seems to be ada3, but after shuffling the drives around a couple times, the drive it drops seems to be completely random. Furthermore trying to stress test it I've done multiple simultaneous copies to the computer through windows and it's rock solid for hours on end. It only seems to exhibit this behavior when trying to use windows backup.