[ I |  9/15 04:02:26.578 | 87203 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/15 04:02:26.578 | 87203 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/15 04:02:26.579 | 87203 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/9fb11a5cf7b1fc20b2e02d018615b6ca' to display the log.
[ I |  9/15 04:02:26.578 | 87203 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/15 04:02:26.578 | 87203 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/15 04:02:26.579 | 87203 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/9fb11a5cf7b1fc20b2e02d018615b6ca' to display the log.
[ I |  9/15 04:02:26.582 | 87204 | 4.9 ] mount.quobyte 4.9 (1db25233e74)
[ I |  9/15 04:02:26.582 | 87204 | 4.9 ] Client UUID: br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I
[ I |  9/15 04:02:26.582 | 87204 | 4.9 ] Registry: osci02.corp.quobyte.com:7861
[ I |  9/15 04:02:26.582 | 87204 | 4.9 ] Volume: cinder-vol-a9871b7e-3ab9-4df2-9670-49cc1df124ad
[ I |  9/15 04:02:26.582 | 87204 | 4.9 ] FUSE version: 316
[ I |  9/15 04:02:26.591 | 87204 | 4.9 ] Breakpad initialized (dumping to /root/.quobyte/minidumps)
[ I |  9/15 04:02:26.617 | 87204 | 4.9 ] Setting total object cache size to 2508193792 bytes
[ I |  9/15 04:02:26.617 | 87204 | 4.9 ] Using FUSE low-level API
[ I |  9/15 04:02:26.617 | 87204 | 4.9 ] Caching of uid/gid to user/group name mappings is enabled
[ I |  9/15 04:02:26.617 | 87204 | 4.9 ] Setting up sockets network client, connect timeout (s): 2 linger timeout (s): 1200 request timeout granularity (s): 10
[ I |  9/15 04:02:26.632 | 87230 | 4.9 ] HTTP server started on port 55000
[ I |  9/15 04:02:26.633 | 87204 | 4.9 ] Caching mappings from uid/gid to user/group name and group membership temporarily.
[ I |  9/15 04:02:26.637 | 87204 | 4.9 ] Mount point /opt/stack/data/cinder/mnt/9fb11a5cf7b1fc20b2e02d018615b6ca established
[ I |  9/15 04:02:26.637 | 87204 | 4.9 ] TimeSync is running and remote sync every 60 seconds
[ I |  9/15 04:02:26.651 | 87204 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/15 04:02:26.670 | 87204 | 4.9 ]  `-> suppressed previous message 1 time
[ I |  9/15 04:02:26.670 | 87204 | 4.9 ] Opening volume cinder-vol-a9871b7e-3ab9-4df2-9670-49cc1df124ad (e6abe495-92fe-4454-8e7d-72e39c408a15)
[ I |  9/15 04:02:26.673 | 87204 | 4.9 ] Setting metadata cache size to 500000 based on available system memory of 12 GiB
[ I |  9/15 04:02:26.678 | 87204 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/15 04:02:26.682 | 87236 | 4.9 ] Changed metadata cache configuration for volume e6abe495-92fe-4454-8e7d-72e39c408a15 to cache_ttl_ms: 0 negative_cache_ttl_ms: 0 enable_write_back_cache: false
[ I |  9/15 04:02:26.682 | 87204 | 4.9 ] Failed to invalidate inode: 38: Function not implemented
[ I |  9/15 04:02:26.696 | 87204 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:02:26.701 | 87226 | 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:02:29.631 | 87205 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/15 04:02:36.341 | 87227 | 4.9 ]  `-> suppressed previous message 1 time
[ W |  9/15 04:02:36.341 | 87227 | 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:02:50.923 | 87240 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:02:50.924 | 87226 | 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:03:13.141 | 87245 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:03:13.143 | 87227 | 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:03:45.895 | 87241 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:03:45.900 | 87229 | 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:04:36.449 | 87242 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:04:36.451 | 87229 | 4.9 ] Request 13001:1 (19) 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:05:38.028 | 87243 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:05:38.030 | 87229 | 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:06:39.742 | 87244 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:06:39.744 | 87226 | 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:07:38.623 | 87246 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:07:38.627 | 87227 | 4.9 ] Request 13001:1 (33) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=37: error_type: INVALID_STATE error_message: "CLIENT br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:08:40.439 | 87239 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:08:40.442 | 87227 | 4.9 ] Request 13001:1 (37) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=42: error_type: INVALID_STATE error_message: "CLIENT br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:09:38.647 | 87240 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:09:38.649 | 87228 | 4.9 ] Request 13001:1 (42) 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:10:36.765 | 87245 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:10:36.769 | 87229 | 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:11:33.811 | 87241 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:11:33.813 | 87226 | 4.9 ] Request 13001:1 (52) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=57: error_type: INVALID_STATE error_message: "CLIENT br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:12:35.848 | 87242 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:12:35.850 | 87227 | 4.9 ] Request 13001:1 (57) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=62: error_type: INVALID_STATE error_message: "CLIENT br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:13:34.927 | 87243 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:13:34.928 | 87228 | 4.9 ] Request 13001:1 (62) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=66: error_type: INVALID_STATE error_message: "CLIENT br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 04:14:36.322 | 87244 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 04:14:36.325 | 87228 | 4.9 ] Request 13001:1 (66) 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 br2rXAIc-nxc4-RdF2-QvDv-ePZBQrZnuT2I does not support enabled feature FILE_FORMAT_V3, please update it"