I don't know what might have caused the problem, and it hasn't happened again.
Windows was not involved. I've never tried to use rdiff-backup under Microsoft
Windows or with any Windows filesystem.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
On 1/14/23 12:32 AM, EricZolf wrote:
Hi Robert,
were you able to reproduce the issue with the "persistent lock"?
Is Windows involved in this issue by chance? I had the issue during early
phases of my development, that stopped processes were still recognized as
running under Windows.
KR, Eric
On 02/01/2023 07:55, Eric Zolf wrote:
Hi,
On 02/01/2023 00:56, Robert Nichols wrote:
I got a message that another rdiff-backup process with PID xxxx was running in that archive, coupled with a warning
that running two rdiff-backup processes simultaneously could result in severe corruption of the archive. rdiff-backup
then suggested that running with "--force" would bypass the restriction, and exited with an error status. As
I said, that PID did not exist on either the client or the server. In fact, there was no other rdiff-backup process
running anywhere on my network. I looked for a possible ".lock" file and did not find any. There was an empty
"lock.xxx" (I forget what "xxx" was), which I tried removing, to no avail.
Sorry, my bad, the lockfile is named indeed `rdiff-backup-data/lock.yml`, but I
still need more information to repeat the issue.
