The destination for incoming CrashPlan backups on my server (11.04) is

/media/SeagateBig

(SeagateBig is the volume name of my 2TB USB drive).

When the server boots, two things happen: 1) SeagateBig auto-mounts and 2) CrashPlan starts.

The problem is, that often these two things don't happen in that order. Then I get:

• Crashplan starts
• looks for /media/SeagateBig
• doesn't find it
• instead of waiting for it, CREATES IT

Now it's backing up onto my / filesystem. NOT COOL.

Meanwhile, when SeagateBig finally gets around to mounting, it finds that /media/SeagateBig already exists, shrugs, and creates /media/SeagateBig_ as its mount point.

What I need is a way for the order to be enforced - where SeagateBig mounts and then and only then the CrashPlan service is started.

Unless I learn that CrashPlan can be told to wait for its destination directory, never to create it... which I am also investigating. But the CrashPlanEngine script is installed by the product so I am loath to modify it, as I know I could by having it loop until df greps successfully for "SeagateBig".