NFS tuning on FreeBSD
Hi, I've recently been attempting to tune NFS on machines in our office, which mount /home from a single server. I've hit a sort of impasse, and I don't know why my changes are making any difference to read/write speeds. The situation: Our office has multiple Linux workstations. They can write 256MB to a home directory (NFS mounted) in ~45 seconds when NFSv3 is enabled, and write the same data in about ~1:30 when I force them to use NFSv2. (I have taken the necessary steps to ensure that disk caching does not befuddle these results, and not changed any other options on the server or client side. Also, the NFS server is running Linux.) When I force NFSv2 on our FreeBSD machines, it writes the data in about ~1:30. When I specify NFSv3, it writes 256MB in about ~1:40! Please note that the settings on the server did not change, and I mimicked the Linux clients' settings in FreeBSD. Does anyone have any experience tuning NFS mounts on FreeBSD machines? -- Devin Heckman System Administrator RSSP-IT-NI, UC Berkeley signature.asc Description: Digital signature
Re: NFS tuning on FreeBSD
On 19:21 Tue 29 May , Christopher Hilton wrote: Not sure if you have tried this but the first thing that I try when dealing with NFS is using tcp mounts rather than udp. Most of the black magic of NFS tuning seems to center around compensating for lost udp fragments on the network. I discovered TCP mounts when I was attempting Hi Chris, Thanks for your input here, I will test with TCP rather than UDP. I think I already investigated this route, but it may be worth another shot. Is there any way that you know of to detail information about the NFS mount on a client box? For example, using `mount' in Linux will show all the options with which filesystems (NFS and otherwise) are mounted, but `mount' in FreeBSD does not display these options. Specifically, I want to know what version of NFS the connection is running over, whether or not it's using TCP or UDP, and other information of that nature. I haven't quite found a utility or file that contains this information yet. Thanks, -- Devin Heckman System Administrator RSSP-IT-NI, UC Berkeley signature.asc Description: Digital signature
Server vendors
Hi, The organization I work for is looking to purchase hardware that will serve as a backup server running FreeBSD. We have purchased from IBM for many years, but we are looking at branching out and purchasing from a vendor which explicitly supports FreeBSD. I have been looking at http://www.freebsdsystems.com/ recently, and am wondering if anyone on this list has any experience with this vendor. If not, from whom do you recommend buying hardware for a FreeBSD server? We look for good service contracts (on-site hardware support available, for example) as well as reliable hardware. (Though this may not be necessary, we're looking at buying something that can handle the backup of greater than 20 and less than 40 servers, but remain under a budget of $5k. We think we'll need ~1TB of storage space. Needless to say, we don't need state-of-the-art hardware to accomplish this.) Thanks a bunch! -- Devin Heckman System Administrator RSSP-IT-NI, UC Berkeley signature.asc Description: Digital signature
IPSec, ipfw, and natd
Hi, I recently tried to set up a computer to act as a NAT using FreeBSD 6.1. ipfw functions as it should, as well as IPSec, but I've run into some problems when setting up the NAT. I have two computers behind it, both of which do not need to speak IPSec (and aren't configured to do so). The NAT computer should speak IPSec with one other computer, from which it mounts home directories via NFS. When I enable natd, ipfw, and IPSec, the connection to the computer with which I speak IPSec breaks, but the NAT functions properly (can ping everything except the IPSec-speaking NFS server). My ipfw rules look like this: $cmd 0001 allow udp from any to any isakmp $cmd 0002 allow esp from $ipsec_servers to me $cmd 0003 allow ah from $ipsec_servers to me $cmd 0004 divert natd all from any to any via sis0 ... $cmd 0015 allow icmp from any to any $cmd 9900 allow all from me to any $cmd 9910 allow all from any to any established $cmd deny log all from any to me And natd.conf, which is called when natd is started in the rc scripts, looks like this: port 8668 interface sis0 log yes Does anyone have any experience with problems such as this? Feel free to ask for anything else that may clarify the problem. Thanks, -- Devin Heckman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
