[ I |  9/14 11:42:08.579 | 87473 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/14 11:42:08.580 | 87473 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/14 11:42:08.580 | 87473 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/596e6a80a886d526207e9f3bc2c8c3b5' to display the log.
[ I |  9/14 11:42:08.579 | 87473 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/14 11:42:08.580 | 87473 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/14 11:42:08.580 | 87473 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/596e6a80a886d526207e9f3bc2c8c3b5' to display the log.
[ I |  9/14 11:42:08.583 | 87474 | 4.9 ] mount.quobyte 4.9 (1db25233e74)
[ I |  9/14 11:42:08.583 | 87474 | 4.9 ] Client UUID: t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs
[ I |  9/14 11:42:08.583 | 87474 | 4.9 ] Registry: osci02.corp.quobyte.com:7861
[ I |  9/14 11:42:08.583 | 87474 | 4.9 ] Volume: cinder-vol-6e2d7506-fbcd-474e-96a7-c1b5ac5fd0b0
[ I |  9/14 11:42:08.583 | 87474 | 4.9 ] FUSE version: 316
[ I |  9/14 11:42:08.588 | 87474 | 4.9 ] Breakpad initialized (dumping to /root/.quobyte/minidumps)
[ I |  9/14 11:42:08.613 | 87474 | 4.9 ] Setting total object cache size to 2508193792 bytes
[ I |  9/14 11:42:08.613 | 87474 | 4.9 ] Using FUSE low-level API
[ I |  9/14 11:42:08.613 | 87474 | 4.9 ] Caching of uid/gid to user/group name mappings is enabled
[ I |  9/14 11:42:08.614 | 87474 | 4.9 ] Setting up sockets network client, connect timeout (s): 2 linger timeout (s): 1200 request timeout granularity (s): 10
[ I |  9/14 11:42:08.626 | 87500 | 4.9 ] HTTP server started on port 55000
[ I |  9/14 11:42:08.627 | 87474 | 4.9 ] Caching mappings from uid/gid to user/group name and group membership temporarily.
[ I |  9/14 11:42:08.628 | 87474 | 4.9 ] Mount point /opt/stack/data/cinder/mnt/596e6a80a886d526207e9f3bc2c8c3b5 established
[ I |  9/14 11:42:08.628 | 87474 | 4.9 ] TimeSync is running and remote sync every 60 seconds
[ I |  9/14 11:42:08.641 | 87474 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 11:42:08.658 | 87474 | 4.9 ]  `-> suppressed previous message 1 time
[ I |  9/14 11:42:08.658 | 87474 | 4.9 ] Opening volume cinder-vol-6e2d7506-fbcd-474e-96a7-c1b5ac5fd0b0 (e56dbec4-ac58-466f-b03b-2c720673d2c4)
[ I |  9/14 11:42:08.661 | 87474 | 4.9 ] Setting metadata cache size to 500000 based on available system memory of 12 GiB
[ I |  9/14 11:42:08.666 | 87474 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 11:42:08.671 | 87503 | 4.9 ] Changed metadata cache configuration for volume e56dbec4-ac58-466f-b03b-2c720673d2c4 to cache_ttl_ms: 0 negative_cache_ttl_ms: 0 enable_write_back_cache: false
[ I |  9/14 11:42:08.671 | 87474 | 4.9 ] Failed to invalidate inode: 38: Function not implemented
[ I |  9/14 11:42:08.690 | 87474 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:42:08.696 | 87496 | 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:42:11.620 | 87476 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 11:42:18.403 | 87497 | 4.9 ]  `-> suppressed previous message 1 time
[ W |  9/14 11:42:18.403 | 87497 | 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:42:33.579 | 87511 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:42:33.580 | 87496 | 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:42:54.971 | 87510 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:42:54.974 | 87497 | 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:43:27.105 | 87514 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:43:27.108 | 87499 | 4.9 ] Request 13001:1 (15) 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:44:18.046 | 87515 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:44:18.048 | 87498 | 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:45:17.402 | 87516 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:45:17.403 | 87499 | 4.9 ] Request 13001:1 (23) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=29: error_type: INVALID_STATE error_message: "CLIENT t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:46:18.269 | 87512 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:46:18.271 | 87497 | 4.9 ] Request 13001:1 (29) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=34: error_type: INVALID_STATE error_message: "CLIENT t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:47:17.229 | 87513 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:47:17.231 | 87498 | 4.9 ] Request 13001:1 (34) 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:48:16.580 | 87509 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:48:16.583 | 87498 | 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:49:15.552 | 87511 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:49:15.554 | 87499 | 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:50:15.483 | 87510 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:50:15.485 | 87496 | 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:51:18.099 | 87514 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:51:18.101 | 87497 | 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:52:18.024 | 87515 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:52:18.027 | 87498 | 4.9 ] Request 13001:1 (58) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=63: error_type: INVALID_STATE error_message: "CLIENT t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:53:20.804 | 87516 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:53:20.806 | 87499 | 4.9 ] Request 13001:1 (63) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=67: error_type: INVALID_STATE error_message: "CLIENT t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:54:22.869 | 87512 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:54:22.872 | 87499 | 4.9 ] Request 13001:1 (67) 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 t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 11:55:20.637 | 87513 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 11:55:20.639 | 87496 | 4.9 ] Request 13001:1 (72) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=77: error_type: INVALID_STATE error_message: "CLIENT t5RBKnE8-biO0-S9l2-Dknt-9MuGuVLszmDs does not support enabled feature FILE_FORMAT_V3, please update it"