> On Feb 12, 2020, at 11:08 AM, Jason Dillaman <jdillama@xxxxxxxxxx> wrote: > > On Wed, Feb 12, 2020 at 2:06 PM Yiming Zhang <yzhan298@xxxxxxxx> wrote: >> >> >> >>> On Feb 12, 2020, at 1:24 AM, kefu chai <tchaikov@xxxxxxxxx> wrote: >>> >>> On Wed, Feb 12, 2020 at 3:33 AM Yiming Zhang <yzhan298@xxxxxxxx> wrote: >>>> >>>> The fio-3.17-116-gf4cd, compiled from source. >>> >>> which librados was fio engine compiled with? the v2 msgr was >>> introduced by nautilus (v14). >> >> Compiled with both >> usr/bin/librados-config 10.2.11 (e4b061b47f07f583c92a050d9e84b1813a35671e) >> and v14.0.0-16058-geb4513a (eb4513a62aec3d80f739b9c1ff1374a559bf6b0f) octopus (dev) >> The problem persists. > > If you run "ldd" against your fio binary, which librados2.so is it > picking up? If you have a 10.2.11 librados2.so on your system higher > in your library search path, it will be used. Yes, I can see the shared libs: librbd.so.1 => /usr/lib/x86_64-linux-gnu/librbd.so.1 (0x00007fa3a4e4a000) librados.so.2 => /usr/lib/x86_64-linux-gnu/librados.so.2 (0x00007fa3a4af9000) I recompiled ceph and make install all libs, and got memory issue with fio: fio-3.17-116-gf4cd Starting 1 process Segmentation fault (core dumped) -ym > >> Maybe the we I compile fio is wrong? How should I specify the librados version in fio compilation? >> >> Thanks, >> Yiming >>> >>> also, would be better if you could avoid top-posting. >>> >>>> >>>> Available IO engines: >>>> splice >>>> rados >>>> rbd >>>> http >>>> >>>> Thanks, >>>> Yiming >>>> >>>>> On Feb 11, 2020, at 11:03 AM, Sam Just <sjust@xxxxxxxxxx> wrote: >>>>> >>>>> version of fio are you us >>>> _______________________________________________ >>>> Dev mailing list -- dev@xxxxxxx >>>> To unsubscribe send an email to dev-leave@xxxxxxx >>> >>> >>> >>> -- >>> Regards >>> Kefu Chai >> _______________________________________________ >> Dev mailing list -- dev@xxxxxxx >> To unsubscribe send an email to dev-leave@xxxxxxx >> > > > -- > Jason _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
