os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Add 2014Q1 status report on the OpenAFS port

Browse source 
Submitted by:	bjk
This commit is contained in:
Gabor Pali 2014-04-03 23:00:29 +00:00
parent 816cfb90a8
commit 68044d5c07
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=44431
1 changed files with 45 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

46
en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml
View file

@ -18,7 +18,7 @@
<!-- XXX: Keep the number of entries updated -->
<p>Thanks to all the reporters for the excellent work! This report
contains 8 entries and we hope you enjoy reading it.</p>
contains 9 entries and we hope you enjoy reading it.</p>
<p>The deadline for submissions covering between April and
June 2014 is July 7th, 2014.</p>
@ -537,4 +537,48 @@
prime time at BSDCan&nbsp;2014.</task>
</help>
</project>
<project cat='ports'>
<title>OpenAFS on &os;</title>
<contact>
<person>
<name>
<given>Benjamin</given>
<common>Kaduk</common>
</name>
<email>bjk@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://openafs.org">OpenAFS homepage</url>
</links>
<body>
<p>AFS is a distributed network filesystem that originated from
the Andrew Project at Carnegie-Mellon University. OpenAFS is an
open-source implementation of the AFS protocol derived from IBM
AFS, which was released under the IBM Public License. OpenAFS
on &os; (the <tt>net/openafs</tt> port) is suitable for light
use, but is not yet production ready.</p>
<p>We got a chance to pick up this porting project after some
hiatus. Recent work focused on investigating the bugs preventing
the use of a disk cache for caching file data. An internal
"lookupname" abstraction was intended to return an unlocked,
referenced vnode, but instead returned a locked, referenced
vnode, leading to various failure modes depending on the number
of kernel debugging options enabled.</p>
</body>
<help>
<task>Track down an issue involving incorrect reference counts on
the AFS root vnode that cause warnings on shutdown.</task>
<task>Audit the locking in all the vnode operations code &mdash;
it is expected that there remain some incorrectly locked areas,
though none that present visible issues under light load.</task>
</help>
</project>
</report>