Date: Fri, 03 Sep 1999 20:02:29 +0100 From: Stuart Henderson <stuart@eclipse.net.uk> To: Troy Settle <st@i-plus.net> Cc: James <jrsysadmin@empireone.net>, freebsd-isp@FreeBSD.ORG Subject: Re: anyone run an isp with freebsd Message-ID: <37D01B45.F97E8210@eclipse.net.uk> References: <NDBBKPEMLJEBDEPFNHOHGEAMCAAA.st@i-plus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> NFS does work after a fashion, but there are problems with locking. Anyone know which side of things the locking probs are? OpenBSD locking works on the server side but not client side, if it's the other way round here then maybe there's some light. :-) BSDI does do locking both sides okay iirc. > The second RAID application that we might consider, would be a > monster squid box. But, a handfull of disks and ccd should do the > trick nicely for that application. Let squid do the disk handling itself, it works very well itself, If you need to split the squid into two boxes, you can just take one cache disk out and put it into the second server. You don't have to have one mother of a filesystem to fsck all in one go if it panics, just a load of separate ones all on separate disks that can be checked in parallel. And if a disk dies, you don't have degraded performance while the raid mends itself after you add a new one. Squid 2.3-devel is starting to abstract the filesystem so that they can experiment with alternative filesystems - presumably some day you'll be able to use raw devices directly and bypass UFS (like Peregrine already does). -sh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37D01B45.F97E8210>