NSLU2-Linux
view · edit · print · history

HowTo.DiagnoseAndFixBackupProblems History

Hide minor edits - Show changes to markup

March 31, 2005, at 02:12 AM by JimTucker --
Added lines 9-10:


March 31, 2005, at 02:11 AM by JimTucker --
Changed line 3 from:
  • One or more backup jobs on an unslung slug no longer run, and/or
to:
  • one or more backup jobs on an unslung slug no longer run
Changed line 5 from:
  • You cannot modify an existing backup job in the standard Linksys web administration page.
to:
and/or
Changed lines 7-9 from:
Note: merely rebooting the slug resolves nothing.
to:
  • you cannot modify an existing backup job in the standard Linksys web administration page.
Note: merely rebooting the slug resolves nothing
March 31, 2005, at 02:06 AM by JimTucker --
Changed line 45 from:

(Credit to Ian White for identifying the procedure)

to:

Credit to Ian White for identifying the procedure

March 31, 2005, at 02:03 AM by JimTucker --
Changed line 7 from:
Note: merely rebooting the slug resolves nothing.
to:
Note: merely rebooting the slug resolves nothing.
March 31, 2005, at 02:01 AM by JimTucker --
Changed line 39 from:
How do backup jobs go awry? How does one help to prevent them from doing so? I don't have the answers yet, but I invite those with greater understanding to add to this wiki.
to:
How do good backup jobs go bad? How does one help to prevent them from doing so? I don't have the answers yet, but I invite those with greater understanding to add to this wiki.
March 31, 2005, at 01:57 AM by JimTucker --
Changed lines 1-45 from:
to:

Symptoms

  • One or more backup jobs on an unslung slug no longer run, and/or
  • You cannot modify an existing backup job in the standard Linksys web administration page.
Note: merely rebooting the slug resolves nothing.




Solution

Delete the lock file(s) for the wayward backup job(s).




Procedure

  1. Locate the /share/hdd/conf/mnt/backup directory that records the running state of each backup job.
  2. For each backup job there is a directory of the same name and a "lock" file called <your_backup_job_name>.pid representing the /usr/sbin/backup process. Locate the directory and the file for each wayward job.
  3. Use ps -eaf to verify that /usr/sbin/backup is not actually running.
  4. Delete the pid file(s) for your job(s).
  5. Optional: delete the directory for each job also.




Cause and Prevention

How do backup jobs go awry? How does one help to prevent them from doing so? I don't have the answers yet, but I invite those with greater understanding to add to this wiki.




(Credit to Ian White for identifying the procedure)

view · edit · print · history · Last edited by JimTucker.
Originally by JimTucker.
Page last modified on April 14, 2005, at 10:26 PM