On Mon, May 15, 2017 at 6:35 PM, Sage Weil <sage@xxxxxxxxxxxx> wrote: > On Mon, 15 May 2017, Aaron Ten Clay wrote: >> Hi Sage, >> >> No problem. I thought this would take a lot longer to resolve so I >> waited to find a good chunk of time, then it only took a few minutes! >> >> Here are the respective backtrace outputs from gdb: >> >> https://aarontc.com/ceph/dumps/core.ceph-osd.150.082e9ca887c34cfbab183366a214a84c.6742.1492634493000000000000.backtrace.txt >> https://aarontc.com/ceph/dumps/core.ceph-osd.150.082e9ca887c34cfbab183366a214a84c.7202.1492634508000000000000.backtrace.txt > > Looks like it's in BlueFS replay. Can you reproduce with 'log max recent > = 1' and 'debug bluefs = 20'? > > It's weird... the symptom is eating RAM, but it's hitting an assert during > relay on mount... > > Thanks! > sage > Sage: Here's the log from osd.1: https://aarontc.com/ceph/ceph-osd.1.log.bz2 I'm not entirely sure the issue was reproduced. The symptom of running away with all the RAM still happens, but there is so much in this log I'm not sure if it has what you're looking for. -Aaron -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
