Ravi: Re-discovered this in my email today, sorry I didn't follow up sooner! (Thanksgiving kinda got in the way. ;)) Are you still observing this behavior, and have you tried it with the latest rc branch? If you're still seeing it, we'd appreciate if you could turn on logging, zip them up, and post it somewhere for us to look at. :) Mimicking the debug settings in vstart (with debugging on, it'll have stuff like debug mds = 20) should do the trick. :) Thanks! -Greg On Sun, Nov 21, 2010 at 2:25 PM, Ravi Pinjala <pstatic@xxxxxxxxx> wrote: > On Sun, Nov 21, 2010 at 2:11 PM, Gregory Farnum <gregf@xxxxxxxxxxxxxxx> wrote: >> On Sun, Nov 21, 2010 at 1:44 PM, Ravi Pinjala <pstatic@xxxxxxxxx> wrote: >>> Ah, that's good to know. >>> >>> How should I start isolating what's causing it? "ceph -w" doesn't >>> indicate that anything's going on, and I'm not sure where to look for >>> more detailed information about what ceph's up to. >>> >>> --Ravi >> Well, if you have logging on you can look and see what they're doing >> (at a pretty low level). If you don't have it on, you can start it by >> using injectargs >> (http://ceph.newdream.net/wiki/Monitor_commands#injectargs, you can >> actually use it on all the systems even though the describes the mds) >> and setting up the appropriate debug options. They're listed here (the >> ones preceded by "debug" :) : >> http://ceph.newdream.net/wiki/Ceph.conf#options_defined_in_src.2Fconfig.cc >> >> Looking at the PG map might also show you something, although that'd >> probably be captured by changing amounts of data showing up via ceph >> -w. >> >> What version of ceph are you running right now? I think there's some >> background scrubbing stuff that got pushed in recently. >> -Greg >> > > Running the latest release (0.23), and the client is ubuntu kernel > 2.6.35-22. I considered that it might be some kind of background > scrubbing, but according to gkrellm it's mostly writes going on, so > that didn't really fit. > -- 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
