Hey guys,
I'm trying to use S3QL as a back end for my bacula backups. What I'd like
to do is use an S3 bucket to actually hold the tapes that bacula writes to.
One thing that I notice is that it's really really slow. I started a backup
last night around 10pm, and this morning it hadn't even finished writing to
a 5GB virutal tape. That's just ridiculously slow. If that were writing to
EBS instead, it could have filled up in about 1/2 hour. It would be great
to be able to backup to S3 without the expense of a huge EBS volume!!
Second thing I noticed is that when I went to list the directory I'm
getting an error message:
[root@ops:~] #ls -lh /backup/tapes/
ls: /backup/tapes/: Transport endpoint is not connected
This is the second time I've seen that happen!
And these are the log entries I'm finding in syslog:
[root@ops:~] #grep s3ql /var/log/messages |grep "Feb 1"
Feb 1 01:57:00 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 04:21:32 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 04:23:10 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 05:08:18 ip-172-30-1-80 journal: mount.s3ql[11175] Dummy-18: [backend
] Encountered BadStatusLine exception (''), retrying call to Backend.
open_read...
Feb 1 05:08:25 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-6: [backend
] Encountered BadStatusLine exception (''), retrying call to Backend.delete
...
Feb 1 05:13:59 ip-172-30-1-80 journal: mount.s3ql[11175] Dummy-18: [backend
] Encountered BadStatusLine exception (''), retrying call to Backend.
open_read...
Feb 1 05:17:19 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 05:17:29 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-3: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 05:19:11 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 05:19:13 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-3: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 05:20:36 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 05:20:37 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-3: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 07:54:59 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 07:56:51 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 07:59:14 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:01:57 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:04:09 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:06:22 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:09:02 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:10:54 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:12:53 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:15:25 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:17:04 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:19:45 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 08:22:50 ip-172-30-1-80 journal: mount.s3ql[11175] Thread-4: [backend
] Encountered BadStatusLine exception (''), retrying call to ObjectW.close
...
Feb 1 15:00:22 ip-172-30-1-80 journal: mount.s3ql[11175] MainThread: [mount
] Encountered exception, trying to clean up...
Feb 1 15:00:22 ip-172-30-1-80 journal: mount.s3ql[11175] MainThread: [mount
] Unmounting file system...
Feb 1 15:04:29 ip-172-30-1-80 journal: mount.s3ql[11175] MainThread: [mount
] Exception during cleanup:
Feb 1 15:04:30 ip-172-30-1-80 journal: mount.s3ql[11175] MainThread: [root]
Uncaught top-level exception:
And what I find is that I'll have to run fsck.s3ql and enter 'continue' in
order to get the s3 bucket mounted again on my local file system.
This is the s3ql mount command that I'm giving:
mount.s3ql --log=syslog --cachedir=/cache --allow-other s3://jf-backup /
backup/tapes
I'm using S3QL 1.18.1.
I'd appreciate any help I can find on how to get s3 mounted using s3ql
without running into the transport error! And if ther's some advice on how
to speed things up so that backups don't take forever, I would appreciate
that too!
Thanks
--
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.
