Date: Tue, 13 Feb 2007 14:20:22 -0500 From: Jim Rees <rees@umich.edu> To: Christopher Arnold <chris@arnold.se> Cc: freebsd-fs@freebsd.org, Ivan Voras <ivoras@fer.hr> Subject: Re: UFS2 with SAN Message-ID: <20070213192022.GA15500@citi.umich.edu> In-Reply-To: <20070213192906.U726@chrishome.localnet> References: <45CD6FF5.8070007@freebsd.org> <20070213075627.63126.qmail@web34502.mail.mud.yahoo.com> <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB4@ms05.mailstreet2003.net> <a969fbd10702130839j727d055bu10c3ec80e38d2a3d@mail.gmail.com> <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB5@ms05.mailstreet2003.net> <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB6@ms05.mailstreet2003.net> <45D1F30A.6080403@freebsd.org> <eqsut3$6a3$1@sea.gmane.org> <20070213192906.U726@chrishome.localnet>
next in thread | previous in thread | raw e-mail | index | archive | help
Afs does make a very nice web back end, but there is enough administrative overhead that you might not want it just for web service. It works particularly well if your working set fits in the cache (I suppose that's true of most things). It wouldn't take much to get OpenAFS in pretty good shape on FreeBSD. It mostly has some locking and vnode ref count issues that shouldn't be too hard to fix for someone who knows what they're doing. I'd be happy to point anyone in the right direction.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070213192022.GA15500>