On Aug 12 2016, Brandon Orwell <[email protected]> wrote:
> I had an Amazon S3 filesystem mounted in /mnt/s3qlbackup1. I was copying
> files via "rsync" to it, interrupted the rsync, and then "fusermount -u
> /mnt/s3qlbackup1" to unmount it.
Well, why? There is umount.s3ql for this purpose.
>> File "src/cursor.c", line 990, in APSWCursor_execute.sqlite3_prepare
>>
>> File "src/statementcache.c", line 386, in sqlite3_prepare
>>
>> apsw.BusyError: BusyError: database is locked
>>
>>
> I am unable to mount the filesystem now. The rsync/cp process was killed
> prior to unmounting it. Why is this error occurring and, most importantly,
> how do I remedy it?
As the documentation says,
| If, for some reason, the umount.sql command does not work, the file
| system can also be unmounted with fusermount -u -z. Note that this
| command will return immediately and the file system may continue to
| upload data in the background for a while longer.
Your mount.s3ql process is still running and using the database file.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
