The bad part about my girlfriend moving in with me is that my friend who was living with me left and took our local sever with him. We had combined our spare hardware to build us a server and used his old computer because he had 4 ATA controllers and I had only 2. So now I had to configure my old PC to create a new server (’cause you just can’t live without one of those :) and bought an extra 1.5TB hard disk. That caused quite some trouble. Since the first wasn’t properly detected by my onboard SATA controller I returned it and the replacement seemed to work, only to be mounted as read-only after formatting it. After a while the disk wasn’t properly detected at all. I was surprised with two new disks having the exact same problem, fortunately so was the owner of the web shop where I bought it. He actually called me personally to discuss the situation and concluded that my SATA controller was probably to old to work properly with this big modern disk. So I bought an PCI eSATA controller which solved my problems.
Last weekend I took this card to my friend who also bought a new hard disk and was experiencing similar problems. After I put the card back my big disk wouldn’t mount anymore, though it worked fine when I booted the Ubuntu Live CD. Long story short (live cd: works, reinstall ubuntu: works, dist-upgrade: broken, reinstall: works, reboot: broken) there we suddenly some errors in the FS which fsck managed to fix.
Anyway, most of you aren’t at all interested in the above snipped of my life and want some technical information. Which you are going to get in the remaining part of this post. Hey, the benefit of people blogging technical stuff on their personal blog is that you have to read through the irrelevant stuff. Nothing is perfect, right?
Setting up ubuntu as an file server
I followed a great tutorial to set up AFP on my server which was very easy and everything works like a charm. Well, almost everything.
Permissions
Since there are two users connecting to the machine there are files created by both that also need to be accessed by both users. Setting the setgid bit on the shares directories and adding both users to a common group is a start, unfortunately there doesn’t seem to be a way to set the umask for newly created files using netatalk, so in order for other users to be able to write/delete these files I just add the group write permission with a hourly cron job. It’s ugly, but it does the job.
Time Machine
After a short time of backing up with Time Machine I got the infamous error 109. Since this issue seems to have no solution and chances are slim Apple will do something about it since it they do not support it I decided to make only manual backups at night so they can run uninterrupted, and make backups of my time machine sparsebundle in case the backup gets broken. Yes, that does sound kind of redundant. It’s far from ideal, but a workable situation. I don’t need hourly backups anyway, I just want to have something in case of a hard disk crash or something like that.
Yesterday I read that netatalk 2.0.5 adds time machine support! Since the current version of netatalk in the ubuntu repo is still 2.0.4 I removed it and downloaded the netatalk-2.0.5-2 (and libdb4.8 which it depends on and is also not yet in the ubuntu repo) packages from the debian site and installed them with dpkg. This was all much easier than I expected since people on the web were warning others that this is not the proper way to go and everything might get broken and so on. After some initial errors (removing the .AppleDB directories after error -5014 and removing the old sparsebundle as root after error 109 on an partially removed sparsebundle) it now seems to work just fine.
Interesting to note is that with this new time machine support I indeed do not have to create the sparsebundle by hand and that it is now named Granny.sparsebundle (Granny is my laptops name) without the MAC adres. Also interesting is that TM started to continue backing up in a copy of an old backup I made by hand named Granny_macadres.copy.sparsebundle. Apparently the name of the backup is much more flexible nowadays.
Now I’m just going to make backups wireless hourly without paying attention to it (and thus interrupting it when putting my laptop to sleep) as I used to with my old Time Capsule and see if the new version of netatalk solves the problems I had. For now I’ve interrupted the initial backup several times now and it is still running (and continuing every time where it was interrupted). So far so good, I can at least say that it works more reliable than with the previous version of netatalk.
Update: after some initial success backing up to this AFP share is as unreliable as is was before, still getting a lot of 109 errors. Too bad. I decided to just buy an external USB/eSATA case and put the disk in that. It not expensive and works for sure, though I am deeply unhappy with the situation.
