Home > Geeky, Mac OS X > Using RipCord on 10.5? You may want to exclude the .fseventsd directory.

Using RipCord on 10.5? You may want to exclude the .fseventsd directory.

I use a freeware program called RipCord, which uses rsync, to back up my FileVaulted home on both my home and work laptops. Configured correctly, it works very well on 10.4 and also works fine on 10.5 once you exclude the .fseventsd directory (assuming the .fseventsd directory exists in the directory(s) you want to back up.) The .fseventsd directory is new and is the result of Time Machine. Time Machine relies on 10.5’s new FSEvent framework to track what files and folders have changed (and thus needs to be backed up) and the FSEvents framework relies on a single, constantly running daemon process called fseventsd that reads from /dev/fsevents and writes the events to log files on disk (stored in a .fseventsd directory at the root of the volume the events are for). So, 10.5 will create an invisible .fseventsd folder on the root level of your attached hard drive(s). If you’re using FileVault, an .fseventsd directory will also be created inside your FileVaulted home. Since the contents of that folder change frequently, rsync was having problems at the very beginning of my backup runs on 10.5 when I was trying to back up my FileVaulted home.

How I found this is that I’ve been having a number of RipCord errors on my home and work laptops when I’ve tried to run backups. Excluding that folder seems to have fixed the problem (I found out the reasons for it later), so on 10.5, add ~/.fseventsd to the list of excluded folders in RipCord.

Categories: Geeky, Mac OS X
  1. December 1, 2007 at 1:21 am

    Indeed .fseventsd is the hook for time machine’s daemon process.
    You might want to be aware (if you’re not already) that Time Machine will not backup a File Vaulted home folder until you log out and are logged in as another user. However, even then, it backs it up as a separate ‘sparse bundle’
    a new special type of sparse disk image that includes directories within its structure.

    Other issues with Time Machine are monolithic database data structures used by some apps internally. (Entourage for example) minor changes can equal a large blob that is “changed”. (enough that time machine may never get around to finishing its backup while you’re using an app with data structures like that. It will stop when it notices a change, and then re-doublecheck what it wrote already…. and on and on…)
    a File Vaulted home folder is basically the same idea, which is why it will never get backed up unless you log in as another account.
    For this reason, if you want TM to backup the File Vaulted home folder, you’ll need to log out and into another account every now and then.
    It is totally possible to use TM for a FV’d home folder, just not while using that account. (not yet)

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: