You are not logged in.
I'm using borg backup with an external HDD. It used to work, however, today I got the error:
Failed to create/acquire the lock /run/media/[username]/[backup-dir]/lock.exclusive ([Errno 30] Read-only file system: '/run/media/[username]/[backup-dir]/lock.exclusive.c0o9p7at.tmp').
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/borg/archiver.py", line 5159, in main
exit_code = archiver.run(args)
File "/usr/lib/python3.10/site-packages/borg/archiver.py", line 5090, in run
return set_ec(func(args))
File "/usr/lib/python3.10/site-packages/borg/archiver.py", line 168, in wrapper
with repository:
File "/usr/lib/python3.10/site-packages/borg/repository.py", line 200, in __enter__
self.open(self.path, bool(self.exclusive), lock_wait=self.lock_wait, lock=self.do_lock)
File "/usr/lib/python3.10/site-packages/borg/repository.py", line 432, in open
self.lock = Lock(os.path.join(path, 'lock'), exclusive, timeout=lock_wait).acquire()
File "/usr/lib/python3.10/site-packages/borg/locking.py", line 384, in acquire
self._wait_for_readers_finishing(remove, sleep)
File "/usr/lib/python3.10/site-packages/borg/locking.py", line 397, in _wait_for_readers_finishing
self._lock.acquire()
File "/usr/lib/python3.10/site-packages/borg/locking.py", line 137, in acquire
raise LockFailed(self.path, str(err)) from None
borg.locking.LockFailed: Failed to create/acquire the lock /run/media/[username]/[backup-dir]/lock.exclusive ([Errno 30] Read-only file system: '/run/media/[username]/[backup-dir]/lock.exclusive.c0o9p7at.tmp').I haven't changed anything with my HDD or made it read-only. How can I solve this?
Last edited by questionask (2022-10-20 17:12:37)
Offline
Is it read only? 'mount' without parameters or 'cat /proc/mounts' to check. Then the next step would be to check dmesg / journal whether there was an error that caused it to go read only, or USB disconnect and the like. You can also check 'smartctl -a' for generic problems with the drive.
Online
borg.locking.LockFailed: Failed to create/acquire the lock /run/media/[username]/[backup-dir]/lock.exclusive ([Errno 30] Read-only file system: '/run/media/[username]/[backup-dir]/lock.exclusive.c0o9p7at.tmp')
Another instance running (even interrupted) ? See: https://borgbackup.readthedocs.io/en/st … /lock.html
Offline
Both ideas seem not to help:
$ cat /proc/mounts
[...]
/dev/sda1 /run/media/[username]/[backupHDD] ext4 ro,nosuid,nodev,relatime,errors=remount-ro 0 0$ sudo borg break-lock /run/media/[username]/[backupHDD]/[backup-dir]
Local Exception
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/borg/archiver.py", line 5159, in main
exit_code = archiver.run(args)
File "/usr/lib/python3.10/site-packages/borg/archiver.py", line 5090, in run
return set_ec(func(args))
File "/usr/lib/python3.10/site-packages/borg/archiver.py", line 183, in wrapper
return method(self, args, repository=repository, **kwargs)
File "/usr/lib/python3.10/site-packages/borg/archiver.py", line 2274, in do_break_lock
repository.break_lock()
File "/usr/lib/python3.10/site-packages/borg/repository.py", line 416, in break_lock
Lock(os.path.join(self.path, 'lock')).break_lock()
File "/usr/lib/python3.10/site-packages/borg/locking.py", line 441, in break_lock
self._roster.remove()
File "/usr/lib/python3.10/site-packages/borg/locking.py", line 296, in remove
os.unlink(self.path)
OSError: [Errno 30] Read-only file system: '/run/media/[username]/[backupHDD]/[backup-dir]/lock.roster'Offline
Well, it's how the error message suggested:
/dev/sda1 /run/media/[username]/[backupHDD] ext4 ro,nosuid,nodev,relatime,errors=remount-ro 0 0
The filesystem is mounted read-only.
Offline
Thanks. The reason for this seems to be–according to 'mount'–that the file system has errors. I fixed it using
# fsck -p /dev/[my partition]Offline