The 2007 Linux Storage and File Systems Workshop
Posted Mar 21, 2007 2:54 UTC (Wed) by
drag (subscriber, #31333)
In reply to:
The 2007 Linux Storage and File Systems Workshop by saffroy
Parent article:
The 2007 Linux Storage and File Systems Workshop
OpenAFS is, indeed, very nice.
But it's Windows support is crap. Not because OpenAFS is not cool, but because Window uses SMB or Microsoft's DFS to do it's thing and nobody else's. OpenAFS has to use a sort of SMB emulation were it deals with AFS stuff then translates that to something that the system can use.
But if your just dealing with Linux clients then that's not a problem.
Also the file and directory permission model is bizzare and isn't realy compatable with just standard Unix-style ACL (user/group/world read/write/execute) model. So people used to Linux permissions have to relearn how to deal with AFS permissions.
It's not posix, and it's not compatable with special file types like named pipes.
Also there is no real way to access your data unless your AFS server stuff is actually running. OpenAFS tends to incure a higher amount of knowledge and administration stuff isn't very easy to deal with.
Then it's large file performance is realy bad. It's just plain slow and the volumes are very limited in size.
What it's VERY good for is if you have a large distributed network.
Say you have a wireless network or a WAN-wide thing were you have a entire campus of computers to take care off. It handles disconnection very well, it's caching support is very good for semi-offline work (ie you can still edit a file even if you temporarially lost contact with the servers.
It's security stuff is nice. The volume management is very nice, snapshotting and mirroring stuff. It's safe to use over the internet and unencrypted wireless networks.
And as a special bonus it's /afs/ directory tree is very handy. It allows people to move volumes around, change servers, setup mirrors, and all sorts of stuff without having to have the clients know of any of these changes. Were as with NFS or SAMBA if you change out file servers or whatnot then the clients all have to be reconfigured to know the new locations and names of the servers and directories. With OpenAFS this is not nessicary.
But considuring the lack of posix support and poor large file performance as well as permission issues it's not realy a replacement for NFS. It's a alternative that is usefull in places were NFS is not.
And it's poor Windows support means that it's not usefull as a replacement for Samba.
But it's nice.
The OpenAFS points out a huge problem for Linux in general though. AFS is ancient. It's old old old. It's like X Windows/Athena/Kerberos ancient. Still, even with it's age, it's still MUCH more sophisticated then NFS or SMB network protocols. Nobody has realy produced anything better.
Lustre, maybe. It certainly has a lot of cool features and is fast. But I don't think that it has any security.
Supports lots of stuff. TCP networking, ininaband, and all sorts of other bizzare interconnects.
Supports ACLs, extended ACLs, extended attributes. Lots of high aviability and high performance features. Failover, extra redudancy. You can use it as root FS. It supports Quotas.
It doesn't require special patches and kernel recompiles for Linux client support.
The only thing that it lacks is robust security. They plan on supporting GSSAPI and Kerberos with the 1.8.0 release. This is due out by the end of this year according to their roadmap...
For Unix and Windows comaptability it supports SMB and NFS v2/v3/v4 export.
(
Log in to post comments)