I actually thought this [post=28793]post[/post] was the latest & greatest. Maybe that's not for slow directory browsing though?Which posting above did you use the settings from? Post #5 or #7?
[thread=7637]Case in point[/thread]. A single disk can/will pull the entire pool down.I have seen people with hardware problems (bad or failing disks) have problems with slow transfer speeds.
I'd run some long smart tests against all the disks and see if that turns anything up.I did have one of my disks fail a few weeks ago, but I got a replacement and it reslivered a-ok. Zpool status is good (checked from the CLI).
socket options = SO_RCVBUF=131072 SO_SNDBUF=131072
kern.ipc.maxsockbuf = 16777216 net.inet.tcp.recvbuf_max = 16777216 net.inet.tcp.sendbuf_max = 16777216
Leaving it out, any noticeable change?Extended SMART tests for all 4 disks come up clean. I've figured out that the "max xmit" variable in CIFS causes samba to exit on signal 6.
I recently read a recommendation, for Samba, to turn off atime for directories with a very large number of files.However, browsing my single CIFS share is quite slow, directory listings (especially my 19000+ file MP3 folder) are slow.
Deaks2 if you are still looking for this, you turn of atime under ZFS options for the dataset. You can also double check that Win7 isn't trying to index anything on the share. What's the view option you are using for the music folder anyway?Where would I kill atime? Using the Samba conf file?
socket options = SO_RCVBUF=131072 SO_SNDBUF=131072
kern.ipc.maxsockbuf = 16777216 net.inet.tcp.recvbuf_max = 16777216 net.inet.tcp.sendbuf_max = 16777216
Unless you're Deaks2 in disguise I don't remember helping you. What's more the suggestions I made were a starting point as Samba was crashing on him and not a replacement for everything.I've tried the hints from paleoN (sysctls, CIFS auxilary parameters, atime). Without any result. (Thanks anyway for your help!)
+1It seems like you're missing quite a few of the ones I recommended, you can't just mix and match them. Try them all, then remove or adjust them one at a time (some of them work in groups or pairs).
kern.maxvnodes 250000 kern.coredump 0 kern.dirdelay 4 vfs.zfs.prefetch_disable 0 vfs.zfs.zil_disable 0 vfs.zfs.txg.timeout 5 vfs.zfs.txg.synctime 1 vfs.zfs.vdev.max_pending 35 vfs.zfs.vdev.min_pending 4 vfs.zfs.txg.write_limit_override 1073741824 vfs.nfsrv.async 0 net.inet.tcp.sendbuf_max 16777216 net.inet.tcp.recvbuf_max 16777216
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=98304 SO_SNDBUF=98304 getwd cache = yes
FreeNAS-8.0.4-RELEASE-p1-x64 (11059), boot from USB-stick, 4 GB RAM, 3TB 7200 RPM disks.
The manual isn't kidding about considering UFS until you can afford better hardware either. There's lots of threads in the forum with the answer being "more RAM". You can also review the presentation I have in my signature for other useful common mistakes newbies make. :)The best way to get the most out of your FreeNAS™ system is to install as much RAM as possible. If your RAM is limited, consider using UFS until you can afford better hardware. ZFS typically requires a minimum of 6 GB of RAM in order to provide good performance; in practical terms (what you can actually install), this means that the minimum is really 8 GB. The more RAM, the better the performance, and the Forums provide anecdotal evidence from users on how much performance is gained by adding more RAM. For systems with large disk capacity (greater than 6 TB), a general rule of thumb is 1GB of RAM for every 1TB of storage.
NOTE: by default, ZFS disables pre-fetching (caching) for systems containing less than 4 GB of usable RAM. Not using pre-fetching can really slow down performance. 4 GB of usable RAM is not the same thing as 4 GB of installed RAM as the operating system resides in RAM. This means that the practical pre-fetching threshold is 6 GB, or 8 GB of installed RAM. You can still use ZFS with less RAM, but performance will be effected.
If you are installing FreeNAS™ on a headless system, disable the shared memory settings for the video card in the BIOS.