OK. This is very frightening. On my live server I had 4 buckets mounted. The largest one was around 80 GB. The buckets were fine and well for around a week, and then the largest one failed with some transport broken message. As it was my live server, I had to revert to s3fs to avoid disruptions. I'm afraid there's not much else I can give about this error as I didn't quite have the time to debug. However, if there are any log files I can provide, let me know. Other than that, this is a real sneaky bug, I have seen it happen before on staging, but just brushed it away as some networking issue.
OK. This is very frightening. On my live server I had 4 buckets mounted. The largest one was around 80 GB. The buckets were fine and well for around a week, and then the largest one failed with some transport broken message. As it was my live server, I had to revert to s3fs to avoid disruptions. I'm afraid there's not much else I can give about this error as I didn't quite have the time to debug. However, if there are any log files I can provide, let me know. Other than that, this is a real sneaky bug, I have seen it happen before on staging, but just brushed it away as some networking issue.