Re: [ceph-users] IO Error reaching client when primary osd get funky but secondaries are ok

Hello David, On Wed, Aug 9, 2017 at 3:08 PM, David Turner wrote: > When exactly is the timeline of when the io error happened? The timeline was included in the email, hour:min:sec resolution. I spared millisecs since it doesn't really change things. > If the primary >

Re: [ceph-users] IO Error reaching client when primary osd get funky but secondaries are ok

When exactly is the timeline of when the io error happened? If the primary osd was dead, but not marked down in the cluster yet, then the cluster would sit there and expect that osd too respond. If this definitely happened after the primary osd was marked down, then it's a different story. I'm

[ceph-users] IO Error reaching client when primary osd get funky but secondaries are ok

Hello, ceph version 0.94.10 (b1e0532418e4631af01acbc0cedd426f1905f4af) We had a few problems related to the simple operation of replacing a failed OSD, and some clarification would be appreciated. It is not very simple to observe what specifically happened (the timeline was gathered from half a