As far as I know there is/was a limitation for AFS volume name length so one can practically use 22 characters only (we use read only volumes as well so we need to fit into the 31 char limit with adding ".readonly"). Does anyone know if this limit still applies for recent OpenAFS releases and if yes, what is the reason for this limitation other than historic? I would really like to be able to use longer names. (Already asked on superuser.com but realized it fits better here).
I'm trying to install and configure an OpenAFS server inside an OpenVZ container. However, when running afs-newcell, it complains that the AFS client cannot be started. It says "AFS module /lib/modules/2.6.32-5-openvz-amd64/fs/openafs.o does not exist."
In the host, I installed openafs-modules-2.6.32-5-openvz-amd6 (from MIT). Doing lsmod | grep afs on host works, and show that openafs module is loaded. Doing the same in the guest doesn't show the module.
I understand that modprobe cannot be run inside a container for stability and security reason, but is there any way of "sharing" some module with a specified guest?
I'm running a small home server that stores my documents. The disks in this server are in a RAID 1 configuration (using Linux md) and it's also periodically being backed up to an external hard drive to make sure I don't lose them. However, I'm always accessing the files from other computers on the home network using an SMB share, and this results in a considerable speed penalty (especially when connected over WLAN). This is quite annoying when editing large files, such as digital camera RAWs, for example.
I've been looking for a solution to this problem. It would have to offer some kind of local caching to speed up the file access. The client would preferably not keep a copy of all data on the server, as it consists of a very large collection of photographs, most of which I will not access frequently. Instead, it should only cache the accessed files and sync the changes back in the background. Ideally, it would also do some smart read-ahead (cache the files that are in the same directory as the currently opened file, for examples), but I suppose that's asking a bit much. Synchronization should be automatic (on file change). Conflicting file changes (at the same time on different clients) are unlikely to happen in my use case, but I would prefer if they are handled properly (notification to the user).
I've come across the following options, so far:
something similar to Dropbox. iFolder seems to be the only thing that comes close, but its reputation (stability) and requirements put me off.
A distributed file system such as OpenAFS. I'm not sure this will speed up file access. It is probably overkill for what I need.
Maybe NFS or even Samba offer these possibilities. I read a bit about Windows' Offline Files, but its operation seems limited (at least on Windows XP).
As this is just for personal use, I'm not willing to spend a lot of money. A free solution would be preferred. Also, the server needs to run on Linux, and I need a client for at least Windows.
Edit: I have since set up OpenAFS (a quite complex process). It seems to cater for most of my needs. Files are cached locally, speeding up access to cached files. First access to a file is still slow, of course. I'm looking forward to Disconnected AFS planned for a future OpenAFS release as this will allow pre-caching of files. This would be perfect for editing sets of large files such as camera RAWs.
I want to enable file sharing between servers and clients, both linux. I don't want to rely on machine trust like in NFSv4 because client users will have root privileges. What are my options besides SMB (SAMBA)? Does OpenAFS support user level authentication & access? Using mounted WebDAV/ftp/sshfs seems silly for LAN.
I am trying to see if OpenAFS fits my needs as a distributed filesystem and is a bit stuck. There are docs but they're all quite hard to understand, so asking for some expert advice here. My questions:
- which version to install? I need windows client support so I need 1.5 - right? But it is not stable.. Or is it? And don't see any pre-built rpms for it, so compiling from sources?
- tried to compile and it worked but it created a non-"mp" kernel module while my kernel needs an mp one - how to workaround that?
- do I really need a new fresh partition to start with or I can re-use an existing one and just make it available via afp?
- any nice HOWTOs around?