Question

2

$local_fs not including all drives

rated 0 times [ 2] [ 0] / answers: 1 / hits: 936 / 1 Year ago, sat, february 4, 2023, 10:04:00

This is a refinement of a question I asked yesterday, the product of deeper research I have done since.

The script that starts CrashPlan has, as it should, a hard dependency on $local_fs in its LSB Required-Start entry. The problem is coming about when this dependency is satisfied without the USB volume being mounted. Therefore CrashPlan thinks it has to create its backup destination and the conflicts begin.

My understanding of $local_fs is that everything in mtab will be mounted before it is satisfied. Is that not the case? Are there options I can add to the mtab entry to change this behavior for the volume in question?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

variark

Add To Favorites

Follow

Total Points: 82

Total Questions: 114

Total Answers: 122

Location: Sweden

Member since Mon, May 8, 2023

1 Year ago

variark questions

1 How do I close the current document in GNOME Text Editor?

Wed, Nov 3, 21, 13:30, 3 Years ago

1 Filename with colon in NTFS

Sun, Jan 8, 23, 16:05, 1 Year ago

1 Tool to remove unnecessary packages

Thu, Dec 15, 22, 02:10, 1 Year ago

1 Why are some snaps fast, and others so slow?

Sun, Jun 26, 22, 12:20, 2 Years ago

1 Python 3.8 won't run "hello" script

Tue, Dec 14, 21, 15:40, 2 Years ago

View All

answered 1 Year ago percol · Accepted Answer

If I recall correctly, USB drives are mounted by udev after virtual-filesystems (an Upstart signal), not as part of $local_fs.

So one solution is a bug against CrashPlan - it's assuming the drive you want to backup is not USB.

A workaround is to change the dependency (or to add a second) is the CrashPlan init script.

Another (easier) workaround is to add a 'sleep 60' or other pause to the CrashPlan init script. Or to simply renumber the symlinks so they run later.