On Sep 14 2015, Martin <[email protected]> wrote:
> Hi,
>
> Every night my mailserver does a backup of the mail store filesystem which
> often (but not allways) results in a waiting fuse process (
> /sys/fs/fuse/connections/25/waiting) leaving the system with a steady load
> of 1, see attachment.
> The s3ql logs for the mailstore mountpoint are littered with these messages:
>
> 2015-09-13 09:14:08.932 [878] Thread-6: [backend] Encountered BadStatusLine
> exception (''), retrying call to Backend.delete...
[...]
This means that something is wrong with the network connection, and S3QL
retries..
> 2015-09-13 09:23:09.387 [878] Dummy-21: [backend] Encountered BadStatusLine
> exception (''), retrying call to Backend.open_read...
> 2015-09-13 10:14:59.053 [878] Thread-4: [backend] Encountered BadStatusLine
> exception (''), retrying call to ObjectW.close...
..but apparently it's successful (or the message wouldn't be
repeated). So these messages are no cause for concern.
> I'm using 1.16-1 because I still haven't found the time to investigate a
> working upgrade path to 2.14, since there is no path from 1.16 to 2.14. But
> that's another issue.
You should be able to go directly to 2.9, and then to 2.13 (each step
requiring a file system upgrade). From there you can go to the current
2.14 (without needing to upgrade the file system).
> Anyway, I was wondering what could cause this stale process? I allways
> fsck both filesystems before mount on reboot, but it feels like
> there's an offending file or block somewhere in the mailstore that
> triggers this problem after some time. Is there a way to find out
> which inode/file is triggering the fuse waiting state in sysfs?
Yes. But it'll be much easier to figure out with a more recent S3QL
version. Would it be possible for you to try to upgrade first?
I think the best way to do this is to install 2.14 from the Ubuntu PPA,
and then download 2.9 and 2.13 from bitbucket. You can extract the
tarballs and just run bin/s3qladm without installing the intermediate
versions.
> As I write this, I see there's a 1.19 release in bitbucket. I use ubuntu
> 14.04 packages from http://ppa.launchpad.net/nikratio/s3ql/ubuntu trusty
> main, why is 1.19 not in that repo?
> I see, you don't support 1.x in that repo,
Yes, Ubuntu trusty can run S3QL 2.x, so there are no 1.x packages
provided.
> it's the ubuntu one I'm seeing
> and that's not updated apparently?
I don't understand this question.
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.
