[ I |  9/14 11:40:53.150 | 87447 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/14 11:40:53.151 | 87447 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/14 11:40:53.151 | 87447 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/bf09c7f5cdfeed63fb821e37840584d5' to display the log.
[ I |  9/14 11:40:53.150 | 87447 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/14 11:40:53.151 | 87447 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/14 11:40:53.151 | 87447 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/bf09c7f5cdfeed63fb821e37840584d5' to display the log.
[ I |  9/14 11:40:53.154 | 87448 | 4.9 ] mount.quobyte 4.9 (1db25233e74)
[ I |  9/14 11:40:53.155 | 87448 | 4.9 ] Client UUID: Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM
[ I |  9/14 11:40:53.155 | 87448 | 4.9 ] Registry: osci02.corp.quobyte.com:7861
[ I |  9/14 11:40:53.155 | 87448 | 4.9 ] Volume: cinder-vol-c7cfba61-0b7b-4138-b2c8-04ca6743a071
[ I |  9/14 11:40:53.155 | 87448 | 4.9 ] FUSE version: 316
[ I |  9/14 11:40:53.162 | 87448 | 4.9 ] Breakpad initialized (dumping to /root/.quobyte/minidumps)
[ I |  9/14 11:40:53.186 | 87448 | 4.9 ] Setting total object cache size to 2508193792 bytes
[ I |  9/14 11:40:53.186 | 87448 | 4.9 ] Using FUSE low-level API
[ I |  9/14 11:40:53.186 | 87448 | 4.9 ] Caching of uid/gid to user/group name mappings is enabled
[ I |  9/14 11:40:53.187 | 87448 | 4.9 ] Setting up sockets network client, connect timeout (s): 2 linger timeout (s): 1200 request timeout granularity (s): 10
[ I |  9/14 11:40:53.200 | 87474 | 4.9 ] HTTP server started on port 55000
[ I |  9/14 11:40:53.200 | 87448 | 4.9 ] Caching mappings from uid/gid to user/group name and group membership temporarily.
[ I |  9/14 11:40:53.201 | 87448 | 4.9 ] Mount point /opt/stack/data/cinder/mnt/bf09c7f5cdfeed63fb821e37840584d5 established
[ I |  9/14 11:40:53.201 | 87448 | 4.9 ] TimeSync is running and remote sync every 60 seconds
[ I |  9/14 11:40:53.218 | 87448 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 11:40:53.237 | 87448 | 4.9 ]  `-> suppressed previous message 1 time
[ I |  9/14 11:40:53.237 | 87448 | 4.9 ] Opening volume cinder-vol-c7cfba61-0b7b-4138-b2c8-04ca6743a071 (2a98b205-4c7a-44a1-95d3-9cabde8f11c0)
[ I |  9/14 11:40:53.239 | 87448 | 4.9 ] Setting metadata cache size to 500000 based on available system memory of 12 GiB
[ I |  9/14 11:40:53.244 | 87448 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 11:40:53.257 | 87481 | 4.9 ] Changed metadata cache configuration for volume 2a98b205-4c7a-44a1-95d3-9cabde8f11c0 to cache_ttl_ms: 0 negative_cache_ttl_ms: 0 enable_write_back_cache: false
[ I |  9/14 11:40:53.257 | 87448 | 4.9 ] Failed to invalidate inode: 38: Function not implemented
[ I |  9/14 11:40:53.312 | 87448 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:40:53.317 | 87470 | 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 Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:40:56.203 | 87451 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 11:41:03.280 | 87471 | 4.9 ]  `-> suppressed previous message 1 time
[ W |  9/14 11:41:03.280 | 87471 | 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 Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:41:18.444 | 87485 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:41:18.447 | 87470 | 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 Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:41:40.189 | 87483 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:41:40.191 | 87471 | 4.9 ] Request 13001:1 (13) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=14: error_type: INVALID_STATE error_message: "CLIENT Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:42:14.225 | 87486 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:42:14.227 | 87472 | 4.9 ] Request 13001:1 (14) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=18: error_type: INVALID_STATE error_message: "CLIENT Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:43:05.215 | 87487 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:43:05.218 | 87472 | 4.9 ] Request 13001:1 (18) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=23: error_type: INVALID_STATE error_message: "CLIENT Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:44:05.511 | 87488 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:44:05.514 | 87473 | 4.9 ] Request 13001:1 (23) 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 Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:45:04.023 | 87489 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:45:04.024 | 87470 | 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 Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:46:04.324 | 87490 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:46:04.330 | 87471 | 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 Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:47:03.064 | 87484 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:47:03.068 | 87472 | 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 Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:48:05.829 | 87485 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:48:05.831 | 87473 | 4.9 ] Request 13001:1 (43) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=47: error_type: INVALID_STATE error_message: "CLIENT Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:49:07.385 | 87483 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:49:07.387 | 87473 | 4.9 ] Request 13001:1 (47) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=52: error_type: INVALID_STATE error_message: "CLIENT Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:50:06.045 | 87486 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:50:06.049 | 87470 | 4.9 ] Request 13001:1 (52) 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 Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:51:06.266 | 87487 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:51:06.268 | 87472 | 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 Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:52:04.224 | 87488 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:52:04.226 | 87470 | 4.9 ] Request 13001:1 (64) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=68: error_type: INVALID_STATE error_message: "CLIENT Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:53:05.673 | 87489 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:53:05.674 | 87470 | 4.9 ] Request 13001:1 (68) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=72: error_type: INVALID_STATE error_message: "CLIENT Lm6AmIN7-0NXd-yUjI-KfzT-odPXErorpXRM does not support enabled feature FILE_FORMAT_V3, please update it"