AFS is a distributed filesystem which offers a client-server architecture, transparent data migration abilities, scalability, a single namespace, and integrated ancillary subsystems.
| Tags | Communications File Sharing Filesystems |
|---|---|
| Licenses | IBM Public |
| Operating Systems | Windows Windows Windows POSIX AIX IRIX Linux Solaris BSD Mac OS X HP-UX |
| Implementation | C |
Recent releases


Changes: A large number of bugfixes (including fixes in the Linux cache manager and the fileserver) are included, as well as a minor new feature enabling gathering information about PAG membership from userspace code. Since pre2, Linux kernel module build issues and a potential NULL pointer dereference in the fileserver have been fixed.


Changes: An MS Hot Fix for Windows Server 2003 SP2 and XP SP3 corrects a deadlock in the SMB redirector. It also adds new functionality that permits the AFS SMB server to be given a longer timeout than normal and a configuration option to allow longer timeouts. Documentation updates and additional documentation were added. The background sync process in the fileserver was updated to avoid a race where a volume would go offline. DragonflyBSD is supported as a userland port. A FreeBSD build problem was fixed. Client locking support on Linux was corrected. Deadlocking during mmap was stopped. Support for OpenBSD 4.5 was added.


Changes: This release contains fixes for the client issues addressed by the security advisories OPENAFS-SA-2009-001 and OPENAFS-SA-2009-002. It also adds support for Linux through kernel 2.6.29 and pre-releases of 2.6.30, dynamic vcache pool allocation on Linux to address issues with inotify(), Solaris cache partition-type-agnostic support for Solaris 9 and later, and Solaris large partition support for file servers. There were also fixes for shutdown issues caused by memory double-freeing and support for multiple local Kerberos realms.


Changes: This release contains fixes for the client issues addressed by the security advisories OPENAFS-SA-2009-001 and OPENAFS-SA-2009-002.


Changes: An all Unix platforms (except Mac OS X 10.4 and 10.5) security fixes were made for the security advisories OPENAFS-SA-2009-001 and OPENAFS-SA-2009-002. Support for pre-release Linux 2.6.30 kernels was added. On Microsoft Windows the service priority class was increased to "High" to match the priority of system components that are dependent upon the a timely response. SMB error responses avoid returning errors that could confuse the Microsoft SMB redirector into disconnecting the connection to \\AFS.
- All comments
Recent commentsRe: Welcome to the present
> While documentation is still OpenAFS'
> weakest point, this project has moved
> forward and is making great progress in
> addressing the outstanding issues.
As a contributor to the OpenAFS project, we welcome any and all feedback on it. I have personally added 28 new man pages to the documentation in the past two years. If you have any issues, please bring them up. Bugs go in the bug tracker and any questions can be answered by the helpful folks on the openafs-info mailing list. If you're confused or just lazy, contact me and I'll help you get to the right place.
Welcome to the present
While documentation is still OpenAFS' weakest point, this project has moved forward and is making great progress in addressing the outstanding issues.
Re: openAFS documentation
I have recently dived into OpenAFS and found the documentation to be amazing. This is a very high quality IBM documentation. You're right, the CD stuff is not up to date, but this is a complexe peace of software, and avoiding the documentation of such software is simply impossible. It aims complexe and heavy environement and therefor cannot be reasonably used with just a RPM. If you have already installed AFS environements in the pas you'll find the documentation to be actually easy to use. I've never done AFS installation before and yet, after two weeks, I had a very nice 12 servers using heavily AFS. Even today, and since AFS is complexe (not OpenAFS, AFS in general), I sometimes read some pieces of this huge 1000+ pages which, again, I consider to be a high quality documentation. there is no doubt for me it is much more important for OpenAFS, today (12/2004), to make OpenAFS better, rather than update here and there to wrong folders or CD stuff indicated in the documentation. I think there are less than ten opensource documentation like this in the world and the IBM fingerprint is clearly there. Make a small effort and you''ll see the only problem is that you have to follow, read, and understand the first server installation, as indicated in the documentation.
Re: openAFS documentation
> I've been studiing open AFS during a
> period of time and at last I have left
> it due to the bad documentation. There
> are several errors in the documentation.
> Beside of this issue the documentation
> referrs to the CD-ROM, but most part of
> the people will download the RPMs from
> the web page. There is no support for
> these people. The RPMs do some of the
> work specified in the installation guide
> but you just have to guess what is
> already done.
>
> The mailing list is also a bit caothic.
In my experience, the documentation was quite good - yes, it did assume you were installing from scratch using a CD, but that just means that you have to actually think, instead of just following instructions. Also, I had to make use of the mailing list once - I got a response back within an hour that solved my problem.
openAFS documentation
I've been studiing open AFS during a period of time and at last I have left it due to the bad documentation. There are several errors in the documentation. Beside of this issue the documentation referrs to the CD-ROM, but most part of the people will download the RPMs from the web page. There is no support for these people. The RPMs do some of the work specified in the installation guide but you just have to guess what is already done.
The mailing list is also a bit caothic.