I'm sorry, which part should I try running with `--fg`? I tried it with
fsck and umount and the options aren't recognised - and I saw '--force' is
an option to fsck so I tried that too (output is below)
Thanks,
Ben
~# fsck.s3ql --fg s3://XXX
usage: fsck.s3ql [-h] [--log <target>] [--cachedir <path>] [--debug-modules
<modules>] [--debug] [--quiet]
[--backend-options <options>] [--version] [--authfile
<path>] [--compress <algorithm-lvl>]
[--keep-cache] [--batch] [--force] [--force-remote]
<storage-url>
fsck.s3ql: error: unrecognized arguments: --fg
~# umount.s3ql --fg /tmp/XXX
usage: umount.s3ql [-h] [--log <target>] [--debug-modules <modules>]
[--debug] [--quiet] [--version] [--lazy]
<mountpoint>
umount.s3ql: error: unrecognized arguments: --fg
~# fsck.s3ql --force s3://XXX
ERROR: Can not check mounted file system.
On Saturday, 13 February 2021 at 12:27:55 UTC [email protected] wrote:
> On Feb 11 2021, Ben Hymers <[email protected]> wrote:
> >
> "/usr/local/lib/python3.8/dist-packages/s3ql-3.7.0-py3.8-linux-x86_64.egg/s3ql/block_cache.py",
>
>
> > line 536, in _queue_upload
> > raise NoWorkerThreads('no upload threads')
> > s3ql.block_cache.NoWorkerThreads: no upload threads
>
> Does it help if you run with `--fg`? If so, you justs need to wait for the
> next release for a proper fix.
>
> Best,
> -Nikolaus
>
> --
> GPG 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/s3ql/337c77f8-7b9b-4e73-99f5-22cdaf645b29n%40googlegroups.com.
