[ I |  9/14 18:31:55.345 | 87411 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/14 18:31:55.346 | 87411 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/14 18:31:55.347 | 87411 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/ff87c4b21b78a4906327ac869e9e481d' to display the log.
[ I |  9/14 18:31:55.345 | 87411 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/14 18:31:55.346 | 87411 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/14 18:31:55.347 | 87411 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/ff87c4b21b78a4906327ac869e9e481d' to display the log.
[ I |  9/14 18:31:55.349 | 87412 | 4.9 ] mount.quobyte 4.9 (1db25233e74)
[ I |  9/14 18:31:55.350 | 87412 | 4.9 ] Client UUID: KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8
[ I |  9/14 18:31:55.350 | 87412 | 4.9 ] Registry: osci02.corp.quobyte.com:7861
[ I |  9/14 18:31:55.350 | 87412 | 4.9 ] Volume: cinder-vol-4cbb6258-c198-427f-aa3c-a1cdae161c20
[ I |  9/14 18:31:55.350 | 87412 | 4.9 ] FUSE version: 316
[ I |  9/14 18:31:55.356 | 87412 | 4.9 ] Breakpad initialized (dumping to /root/.quobyte/minidumps)
[ I |  9/14 18:31:55.382 | 87412 | 4.9 ] Setting total object cache size to 2508193792 bytes
[ I |  9/14 18:31:55.383 | 87412 | 4.9 ] Using FUSE low-level API
[ I |  9/14 18:31:55.383 | 87412 | 4.9 ] Caching of uid/gid to user/group name mappings is enabled
[ I |  9/14 18:31:55.384 | 87412 | 4.9 ] Setting up sockets network client, connect timeout (s): 2 linger timeout (s): 1200 request timeout granularity (s): 10
[ I |  9/14 18:31:55.399 | 87438 | 4.9 ] HTTP server started on port 55000
[ I |  9/14 18:31:55.400 | 87412 | 4.9 ] Caching mappings from uid/gid to user/group name and group membership temporarily.
[ I |  9/14 18:31:55.408 | 87412 | 4.9 ] Mount point /opt/stack/data/cinder/mnt/ff87c4b21b78a4906327ac869e9e481d established
[ I |  9/14 18:31:55.408 | 87412 | 4.9 ] TimeSync is running and remote sync every 60 seconds
[ I |  9/14 18:31:55.422 | 87412 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 18:31:55.441 | 87412 | 4.9 ]  `-> suppressed previous message 1 time
[ I |  9/14 18:31:55.441 | 87412 | 4.9 ] Opening volume cinder-vol-4cbb6258-c198-427f-aa3c-a1cdae161c20 (7e9fd7d0-b6bf-4286-b7e9-b6acd6821d0d)
[ I |  9/14 18:31:55.444 | 87412 | 4.9 ] Setting metadata cache size to 500000 based on available system memory of 12 GiB
[ I |  9/14 18:31:55.450 | 87412 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 18:31:55.457 | 87440 | 4.9 ] Changed metadata cache configuration for volume 7e9fd7d0-b6bf-4286-b7e9-b6acd6821d0d to cache_ttl_ms: 0 negative_cache_ttl_ms: 0 enable_write_back_cache: false
[ I |  9/14 18:31:55.457 | 87412 | 4.9 ] Failed to invalidate inode: 38: Function not implemented
[ I |  9/14 18:31:55.479 | 87412 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:31:55.484 | 87434 | 4.9 ] Request 13001:1 (8) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=9: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:31:58.399 | 87413 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 18:32:05.788 | 87435 | 4.9 ]  `-> suppressed previous message 1 time
[ W |  9/14 18:32:05.787 | 87435 | 4.9 ] Request 13001:1 (9) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=12: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:32:20.963 | 87449 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:32:20.966 | 87434 | 4.9 ] Request 13001:1 (12) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=13: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:32:42.201 | 87448 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:32:42.205 | 87435 | 4.9 ] Request 13001:1 (13) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=15: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:33:14.665 | 87450 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:33:14.667 | 87437 | 4.9 ] Request 13001:1 (15) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=19: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:34:04.721 | 87451 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:34:04.724 | 87437 | 4.9 ] Request 13001:1 (19) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=24: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:35:06.884 | 87452 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:35:06.887 | 87434 | 4.9 ] Request 13001:1 (24) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=28: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:36:09.725 | 87453 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:36:09.730 | 87434 | 4.9 ] Request 13001:1 (28) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=33: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:37:11.965 | 87454 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:37:11.967 | 87435 | 4.9 ] Request 13001:1 (33) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=38: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:38:12.959 | 87447 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:38:12.961 | 87436 | 4.9 ] Request 13001:1 (38) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=43: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:39:14.752 | 87449 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:39:14.755 | 87437 | 4.9 ] Request 13001:1 (43) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=48: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:40:16.141 | 87448 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:40:16.143 | 87434 | 4.9 ] Request 13001:1 (48) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=53: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:41:18.238 | 87450 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:41:18.241 | 87435 | 4.9 ] Request 13001:1 (53) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=58: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:42:16.290 | 87451 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:42:16.292 | 87436 | 4.9 ] Request 13001:1 (58) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=64: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:43:13.635 | 87452 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:43:13.638 | 87434 | 4.9 ] Request 13001:1 (64) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=69: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:44:16.461 | 87453 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:44:16.462 | 87435 | 4.9 ] Request 13001:1 (69) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=74: error_type: INVALID_STATE error_message: "CLIENT KnxBAY4P-IwWe-ef8P-8HMn-GztR95pdLae8 does not support enabled feature FILE_FORMAT_V3, please update it"