Re: LOCK file for rdiff-backup and rdiff-backup-delete

[Eric Zolf]

Hi,

you've probaby got _two_ `current_mirror` files in your repository, 
which signals that a backup is either running or has been interrupted. 
Assuming the latter, the proper way to fix is to run first `rdiff-backup 
regress `/mnt/uSbdisk/FOLDER` (it can take a while), then use 
rdiff-backup-delete to remove the unwanted files.

Hope this helps, Eric

On 11/05/2023 14:39, Dieter Heußner via Any discussion of rdiff-backup 
wrote:
> Hello
>
> when running "rdiff-backup-delete" an error message pops up:
> fail to acquired repository lock. A backup may be running.
>
> However, there is no other backup, neither
> rdiff-backup nor rdiff-backup-delete.
>
> Trying to indentify a LOCK file, for example by
>
> find /mnt/uSbdisk/FOLDER/rdiff-backup-data -iname "*lock* | grep -vi 'block'
> does not show me a LOCK file.
>
> How to drop the mysterious LOCK file?
>
> Best regards
> Dieter
>
> --------------------------------------------------------------
> PGP/GPG Key fingerprint:
> BF12 CD6F EDC4 9FBA C933  316B 2C81 0BEF 4324 8513
> --------------------------------------------------------------