Displaying 6 results from an estimated 6 matches for "fetch_locked_internal".
2018 Sep 18
4
CTDB potential locking issue
...CTDB cluster running on CentOS 7, Samba
4.7.1
The node network is a direct 1Gb link
Storage is Cephfs
ctdb status is OK
It seems to be running well so far but I'm frequently seeing the following
in my log.smbd:
[2018/09/18 19:16:15.897742, 0]
> ../source3/lib/dbwrap/dbwrap_ctdb.c:1207(fetch_locked_internal)
> db_ctdb_fetch_locked for /var/lib/ctdb/locking.tdb.1 key
> DE0726567AF1EAFD4A741403000100000000000000000000, chain 3642 needed 16
> attempts, 315 milliseconds, chainlock: 78.340000 ms, CTDB 236.511000 ms
> [2018/09/18 19:16:15.958368, 0]
> ../source3/lib/dbwrap/dbwrap_ctdb.c:12...
2018 Sep 19
3
CTDB potential locking issue
...> Storage is Cephfs
> >
> > ctdb status is OK
> >
> > It seems to be running well so far but I'm frequently seeing the
> following
> > in my log.smbd:
> >
> > [2018/09/18 19:16:15.897742, 0]
> > > ../source3/lib/dbwrap/dbwrap_ctdb.c:1207(fetch_locked_internal)
> > > db_ctdb_fetch_locked for /var/lib/ctdb/locking.tdb.1 key
> > > DE0726567AF1EAFD4A741403000100000000000000000000, chain 3642 needed 16
> > > attempts, 315 milliseconds, chainlock: 78.340000 ms, CTDB 236.511000 ms
> > > [2018/09/18 19:16:15.958368, 0]
>...
2018 Sep 19
0
CTDB potential locking issue
...e node network is a direct 1Gb link
>
> Storage is Cephfs
>
> ctdb status is OK
>
> It seems to be running well so far but I'm frequently seeing the following
> in my log.smbd:
>
> [2018/09/18 19:16:15.897742, 0]
> > ../source3/lib/dbwrap/dbwrap_ctdb.c:1207(fetch_locked_internal)
> > db_ctdb_fetch_locked for /var/lib/ctdb/locking.tdb.1 key
> > DE0726567AF1EAFD4A741403000100000000000000000000, chain 3642 needed 16
> > attempts, 315 milliseconds, chainlock: 78.340000 ms, CTDB 236.511000 ms
> > [2018/09/18 19:16:15.958368, 0]
> > ../source3/li...
2018 Sep 18
0
CTDB potential locking issue
...>The node network is a direct 1Gb link
>
>Storage is Cephfs
>
>ctdb status is OK
>
>It seems to be running well so far but I'm frequently seeing the
>following
>in my log.smbd:
>
>[2018/09/18 19:16:15.897742, 0]
>> ../source3/lib/dbwrap/dbwrap_ctdb.c:1207(fetch_locked_internal)
>> db_ctdb_fetch_locked for /var/lib/ctdb/locking.tdb.1 key
>> DE0726567AF1EAFD4A741403000100000000000000000000, chain 3642 needed
>16
>> attempts, 315 milliseconds, chainlock: 78.340000 ms, CTDB 236.511000
>ms
>> [2018/09/18 19:16:15.958368, 0]
>> ../source3...
2018 Sep 19
0
CTDB potential locking issue
...>> > ctdb status is OK
>> >
>> > It seems to be running well so far but I'm frequently seeing the
>> following
>> > in my log.smbd:
>> >
>> > [2018/09/18 19:16:15.897742, 0]
>> > > ../source3/lib/dbwrap/dbwrap_ctdb.c:1207(fetch_locked_internal)
>> > > db_ctdb_fetch_locked for /var/lib/ctdb/locking.tdb.1 key
>> > > DE0726567AF1EAFD4A741403000100000000000000000000, chain 3642 needed 16
>> > > attempts, 315 milliseconds, chainlock: 78.340000 ms, CTDB 236.511000
>> ms
>> > > [2018/09/18...
2011 Jul 15
0
S3 and CTDB errors in logs
...187, op=1, reqid=6 : 1 Time(s)
lib/ctdbd_conn.c:940(ctdbd_migrate) ctdbd_migrate: Sending ctdb packet len=324, magic=43544442, vers=1, gen=0, op=0, reqid=6 : 1 Time(s)
lib/dbwrap_ctdb.c:907(db_ctdb_record_destr) Unlocking db 386227600 key 1612000000000000FFFF : 1 Time(s)
lib/dbwrap_ctdb.c:959(fetch_locked_internal) Locking db 386227600 key 1612000000000000FFFF : 2 Time(s)
lib/dbwrap_ctdb.c:996(fetch_locked_internal) ctdb_data.dptr = (nil), dmaster = 4294967295 (0) : 1 Time(s)
lib/messages.c:329(messaging_deregister) Deregistering messaging pointer for type 1 - private_data=(nil) : 20 Time(s)
lib/util_s...