Re: [rdiff-backup-users] Fatal Error: Process still running

[Eric Beversluis]

I tried "--check-destination-dir <backupdir>" and after it ran for about
a half hour gave up. Couldn't tell if it was supposed to be taking that
long or not (rdiff-backup folder was 66GB, I think). I gave up and
started a new backup, since I didn't really need all the diffs.

Thanks. 

EB
On Wed, 2012-03-21 at 10:33 +0100, Maarten Bezemer wrote:
> Usually the --force option wouldn't be necessary. And, most of the times, 
> it's a bad idea.
> If you are sure there is no rdiff-backup process running (either locally 
> or maybe remote using nfs or other network file systems), you can run 
> rdiff-backup --check-destination-dir <backupdir> to clean up the last 
> (failed) backup.
> 
> rdiff-backup saves the process id of the current run in the current_mirror 
> marker file, but that doesn't include a host name and it wouldn't make 
> much sense to check if the directory is mounted over the network.
> 
> So, just make sure there is no rdiff-backup process running, and have it 
> check the destination dir, check its results, and see what a normal backup 
> run will do.
> 
> HTH,
> Maarten
> 
> 
> On Tue, 20 Mar 2012, Eric Beversluis wrote:
> 
> > I guess I need to try to rephrase my question. Basically I need to know
> > what to do about the error message and my next backup. I'd like to know
> > what the "--force" option does before I try it in this case, since the
> > error message seems to imply that using "--force" can cause date
> > corruption. What does "to proceed with regress" mean? Does this mean I
> > would lose all of my diffs? Or does it somehow clear the "running"
> > process so I can proceed with the next rdiff-backup?
> >
> > Thanks.
> >
> > On Mon, 2012-03-19 at 11:41 -0400, Eric Beversluis wrote:
> >> "Fatal Error: It appears that a previous rdiff-backup session with
> >> process
> >> id 2012 is still running.  If two different rdiff-backup processes write
> >> the same repository simultaneously, data corruption will probably
> >> result.  To proceed with regress anyway, rerun rdiff-backup with the
> >> --force option."
> >>
> >> The rdiff-backup seemed to hang the last time it ran it, so I just
> >> aborted it. ps-ef doesn't show any process 2012 or any other
> >> rdiff-backup process running now.
> >>
> >> If I use the --force option, will that abort whatever is happening with
> >> rdiff-backup and start a clean backup?
> >>
> >> Thanks.
> >>
> >>
> >> _______________________________________________
> >> rdiff-backup-users mailing list at address@hidden
> >> https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
> >> Wiki URL: 
> >> http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
> >
> >
> >
> > _______________________________________________
> > rdiff-backup-users mailing list at address@hidden
> > https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
> > Wiki URL: 
> > http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
> >