search

google-code-export / s3ql

Automatically exported from code.google.com/p/s3ql
0 stars 0 forks source link

mount.s3ql crashes when switching network connection #406

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I was rsyncing files over s3ql to google storage when I switched from wired to 
wireless. 

1. The directory where s3ql was mounted now has strange permissions & timestamp:

$ ls -l
ls: cannot access [bucket name]: Transport endpoint is not connected
d????????? ? ?   ?       ?            ? [bucket name]

2. I can't recreate the directory because it still exists though ...
3. mount.s3ql says "Mountpoint does not exist."

As I understand, s3ql isn't built to withstand changes in network connectivity 
at this point but this seems unnecessarily messy.

Original issue reported on code.google.com by jayarmst...@gmail.com on 9 Jul 2013 at 11:05

GoogleCodeExporter commented 9 years ago 
Thanks for reporting this. The mountpoint issue is documented in 
https://code.google.com/p/s3ql/wiki/FAQ#What_does_the_%22Transport_endpoint_not_
connected%22_error

However, I'd be interested to know why changing the network connection caused 
mount.s3ql to crash. Could you post the contents of ~/.s3ql/mount.log right 
before th crash?

Original comment by Nikolaus@rath.org on 9 Jul 2013 at 11:21

GoogleCodeExporter commented 9 years ago 
Here's the entire mount.log as I don't recall exactly when I had that error. 
It's probably the last errors, on July 9th. I don't think I ever managed to 
mount it again.

Original comment by jayarmst...@gmail.com on 18 Jul 2013 at 2:54

Attachments:

GoogleCodeExporter commented 9 years ago 
Hmm. If I disconnect the network, mount.s3ql just hangs. Are you able to 
reproduce this at will? How long does it take between disconnecting (or 
reconnecting?) the network and the crash?

Original comment by Nikolaus@rath.org on 24 Jul 2013 at 3:20

GoogleCodeExporter commented 9 years ago

Original comment by Nikolaus@rath.org on 16 Aug 2013 at 7:29

GoogleCodeExporter commented 9 years ago 
Lacking further information, I'll close this bug for now. Please feel free to 
reopen if you can provide more details.

Original comment by Nikolaus@rath.org on 27 Aug 2013 at 3:33