systematic need of reboot after...

[rmaderna]

I have the following problem and I hope you can help me find a solution or an explanation for it:

While copying "reaally" lots of files (500Giga of pics) to my FreeNAS-8.0-RC3-amd64 installation I'm experiencing the following:

after no more then 30 minutes the file transfer starts to slower until a complete stop.
If I try to access the NAS URL the browser shows no results.
I have to reboot the nas.
This happens always (with this kind of small files transfer).

I believe this to be due to a the really big amount of pics I'm trying to backup, because with bigger files (700M each circa) for a total operation of 500 Giga, the system works correctly (in one occasion it stopped, in truth, but there was a big pics folder to transfer too so.. )

My config:
OS Version: FreeBSD 8.2-RELEASE
Platform: AMD Athlon(tm) II Neo N36L Dual-Core Processor
5 disks 2 Tera each in raidz
CIFS and Windows share
I'm accessing the NAS via Total Commander
PC (Windows 7) and the NAS (HP Proliant) are connected via Gigabit

I'm a linux noob and I installed freeNas using the wizard.

Do you know if this is a known problem?
How can I be more detailed to help find out a cause ?
(please remember I'm a windows user, so I know nothing about linux commands.. but I learn quickly.. usually)
Thanks a lot
Bye!
Riccardo

[protosd]

Experienced the same problem until rebuilding kernel with higher KVA_PAGES and increasing vm.kmem_size.

My system is a Supermicro MBD-X7SPA-H-O with 4GB of RAM.

I think it's more reasonable to expect people to have systems with more than 1 or 2GB of RAM and have a default kernel with this option as a default. Changing this is not trivial for the average user and this makes it difficult for new users that want to embrace FreeNAS.

[jpaetzel]

These options shouldn't be needed on the amd64 capable images. Low memory platforms are not a good choice for ZFS.