2012/5/10 Josef Bacik <josef@xxxxxxxxxx>: > On Fri, Apr 27, 2012 at 01:02:08PM +0200, Christian Brunner wrote: >> Am 24. April 2012 18:26 schrieb Sage Weil <sage@xxxxxxxxxxxx>: >> > On Tue, 24 Apr 2012, Josef Bacik wrote: >> >> On Fri, Apr 20, 2012 at 05:09:34PM +0200, Christian Brunner wrote: >> >> > After running ceph on XFS for some time, I decided to try btrfs again. >> >> > Performance with the current "for-linux-min" branch and big metadata >> >> > is much better. The only problem (?) I'm still seeing is a warning >> >> > that seems to occur from time to time: >> > >> > Actually, before you do that... we have a new tool, >> > test_filestore_workloadgen, that generates a ceph-osd-like workload on the >> > local file system. It's a subset of what a full OSD might do, but if >> > we're lucky it will be sufficient to reproduce this issue. Something like >> > >> > test_filestore_workloadgen --osd-data /foo --osd-journal /bar >> > >> > will hopefully do the trick. >> > >> > Christian, maybe you can see if that is able to trigger this warning? >> > You'll need to pull it from the current master branch; it wasn't in the >> > last release. >> >> Trying to reproduce with test_filestore_workloadgen didn't work for >> me. So here are some instructions on how to reproduce with a minimal >> ceph setup. >> [...] > > Well I feel like an idiot, I finally get it to reproduce, go look at where I > want to put my printks and theres the problem staring me right in the face. > I've looked seriously at this problem 2 or 3 times and have missed this every > single freaking time. Here is the patch I'm trying, please try it on yours to > make sure it fixes the problem. It takes like 2 hours for it to reproduce for > me so I won't be able to fully test it until tomorrow, but so far it hasn't > broken anything so it should be good. Thanks, Great! I've put your patch on my testbox and will run a test over the weekend. I'll report back on monday. Thanks, Christian -- 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
