Re: [ceph-users] Client's read affinity

AFAIK, the OSDs should discover their location in the CRUSH map automatically -- therefore, this "crush location" config override would be used for librbd client configuration ("i.e. [client] section") to describe their location in the CRUSH map relative to racks, hosts, etc. On Tue, Apr 4, 2017

Re: [ceph-users] FreeBSD port net/ceph-devel released

On 4-4-2017 21:05, Gregory Farnum wrote: > [ Sorry for the empty email there. :o ] > > On Tue, Apr 4, 2017 at 12:28 PM, Patrick Donnelly wrote: >> On Sat, Apr 1, 2017 at 4:58 PM, Willem Jan Withagen wrote: >>> On 1-4-2017 21:59, Wido den Hollander wrote:

Re: [ceph-users] FreeBSD port net/ceph-devel released

[ Sorry for the empty email there. :o ] On Tue, Apr 4, 2017 at 12:28 PM, Patrick Donnelly wrote: > On Sat, Apr 1, 2017 at 4:58 PM, Willem Jan Withagen wrote: >> On 1-4-2017 21:59, Wido den Hollander wrote: >>> Op 31 maart 2017 om 19:15 schreef Willem

Re: [ceph-users] FreeBSD port net/ceph-devel released

On Tue, Apr 4, 2017 at 12:28 PM, Patrick Donnelly wrote: > On Sat, Apr 1, 2017 at 4:58 PM, Willem Jan Withagen wrote: >> On 1-4-2017 21:59, Wido den Hollander wrote: >>> Op 31 maart 2017 om 19:15 schreef Willem Jan Withagen :

Re: [ceph-users] FreeBSD port net/ceph-devel released

On Sat, Apr 1, 2017 at 4:58 PM, Willem Jan Withagen wrote: > On 1-4-2017 21:59, Wido den Hollander wrote: >> >>> Op 31 maart 2017 om 19:15 schreef Willem Jan Withagen : >>> >>> >>> On 31-3-2017 17:32, Wido den Hollander wrote: Hi Willem Jan, > Op

Re: [ceph-users] Client's read affinity

Jason, I haven't heard much about this feature. Will the localization have effect if the crush location configuration is set in the [osd] section, or does it need to apply globally for clients as well? On Fri, Mar 31, 2017 at 6:38 AM, Jason Dillaman wrote: > Assuming you

[ceph-users] ceph pg inconsistencies - omap data lost

Hi all, We have a weird issue with a few inconsistent PGs. We are running ceph 11.2 on RHEL7. As an example inconsistent PG we have: # rados -p volumes list-inconsistent-obj 4.19

Re: [ceph-users] Librbd logging

Couple options: 1) you can enable LTTng-UST tracing [1][2] against your VM for an extremely light-weight way to track IO latencies. 2) you can enable "debug rbd = 20" and grep through the logs for matching "AioCompletion.*(set_request_count|finalize)" log entries 3) use the asok file during one

Re: [ceph-users] Get/set/list rbd image using python librbd

Ok, thanks Jason for submitting the feature request ticket. But i am afraid i couldn't contribute now, lack of C/C++ :D On Mon, Apr 3, 2017 at 9:09 PM, Jason Dillaman wrote: > We try to keep the C/C++ and Python APIs in-sync, but it looks like > these functions were

[ceph-users] Librbd logging

Hello cephers, I have a situation where from time to time the write operation to the seph storage hangs for 3-5 seconds. For testing we have a simple line like: while sleep 1; date >> logfile; done & with this we can see that rarely there are 3 seconds or more differences between the

Re: [ceph-users] Troubleshooting incomplete PG's

Hello Sage and Brad, Many thanks for the information >incomplete PGs can be extracted from the drive if the bad sector(s) don't >happen to affect those pgs. The ceph-objectstore-tool --op export command >can be used for this (extract it from the affected drive and add it to >some other osd).

[ceph-users] Why is cls_log_add logging so much?

On a busy cluster, I'm seeing a couple of OSDs logging millions of lines like this: 2017-04-04 06:35:18.240136 7f40ff873700 0 cls/log/cls_log.cc:129: storing entry at 1_1491287718.237118_57657708.1 2017-04-04 06:35:18.244453 7f4102078700 0 cls/log/cls_log.cc:129: storing entry at

Re: [ceph-users] clock skew

Hi John, list, On 1-4-2017 16:18, John Petrini wrote: Just ntp. Just to follow-up on this: we have yet experienced a clock skew since we starting using chrony. Just three days ago, I know, bit still... Perhaps you should try it too, and report if it (seems to) work better for you as well.