severity 983170 grave
tags 983170 + upstream help
thanks
It seems to me that this version cannot simply be distributed as is.
Even, the wrong assumption about trio version compatibility renders it not
compatible with bullseye status.
On Sat, Feb 20, 2021 at 01:24:16PM +0000, Graham Cobb wrote:
Package: s3ql
Version: 3.7.0+dfsg-2
Severity: important
Dear Maintainer,
After upgrading s3ql from 3.3.2+dfsg-1 I suffered from bug #982381 (trio) so
I tried manually installing trio 0.15 (as mentioned in that thread).
Although it allowed some files to be created, any long or complex operation
(such as a backup, or even an `rm -rf` of a large directory) cause a
'Software caused connection abort' error followed by
enormous numbers of 'Transport endpoint is not connected' errors.
In case it was some transient network problem, I used fsck.s3ql to fix the
filesystem and retried - same errors. And the same errors if I (fsck again
and) just try a `rm -rf` on a large directory.
I then tried installing trio 0.18. Same problem.
Mounting is working. fsck is working. Simple file operations are working.
But heavy load causes 'Software caused connection abort'. Completely repeatable.
The following commands reproduce the problem for me:
cd /mnt/mountpoint
count=100
mkdir testdir ; for f in `seq 1 $count` ; do mkdir testdir/$f ; dd
if=/dev/urandom bs=1000 count=1 of=testdir/$f/test status=none ; done
rm -rf testdir
umount /mnt/mountpoint
With the count at 100 the problem occurs when the unmount happens. If the count
is increased to 2000 the problem occurs during the run.
This is using the S3 backend.
By the way, this workload has been working for many years with no problems,
and was working with 3.3.2+dfsg-1 before I decided to try testing 3.7.0+dfsg-2.
--
Francesco P. Lovergine
