[ I |  9/15 09:30:58.750 | 87355 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/15 09:30:58.751 | 87355 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/15 09:30:58.752 | 87355 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/5bd601878e92e764cafb8263a8bf2e6d' to display the log.
[ I |  9/15 09:30:58.750 | 87355 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/15 09:30:58.751 | 87355 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/15 09:30:58.752 | 87355 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/5bd601878e92e764cafb8263a8bf2e6d' to display the log.
[ I |  9/15 09:30:58.755 | 87356 | 4.9 ] mount.quobyte 4.9 (1db25233e74)
[ I |  9/15 09:30:58.755 | 87356 | 4.9 ] Client UUID: RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph
[ I |  9/15 09:30:58.755 | 87356 | 4.9 ] Registry: osci02.corp.quobyte.com:7861
[ I |  9/15 09:30:58.755 | 87356 | 4.9 ] Volume: cinder-vol-c97d1067-6f88-46e5-b7a6-8f47c44d0fab
[ I |  9/15 09:30:58.755 | 87356 | 4.9 ] FUSE version: 316
[ I |  9/15 09:30:58.761 | 87356 | 4.9 ] Breakpad initialized (dumping to /root/.quobyte/minidumps)
[ I |  9/15 09:30:58.788 | 87356 | 4.9 ] Setting total object cache size to 2508193792 bytes
[ I |  9/15 09:30:58.789 | 87356 | 4.9 ] Using FUSE low-level API
[ I |  9/15 09:30:58.789 | 87356 | 4.9 ] Caching of uid/gid to user/group name mappings is enabled
[ I |  9/15 09:30:58.789 | 87356 | 4.9 ] Setting up sockets network client, connect timeout (s): 2 linger timeout (s): 1200 request timeout granularity (s): 10
[ I |  9/15 09:30:58.803 | 87382 | 4.9 ] HTTP server started on port 55000
[ I |  9/15 09:30:58.803 | 87356 | 4.9 ] Caching mappings from uid/gid to user/group name and group membership temporarily.
[ I |  9/15 09:30:58.804 | 87356 | 4.9 ] Mount point /opt/stack/data/cinder/mnt/5bd601878e92e764cafb8263a8bf2e6d established
[ I |  9/15 09:30:58.805 | 87356 | 4.9 ] TimeSync is running and remote sync every 60 seconds
[ I |  9/15 09:30:58.826 | 87356 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/15 09:30:58.847 | 87356 | 4.9 ]  `-> suppressed previous message 1 time
[ I |  9/15 09:30:58.847 | 87356 | 4.9 ] Opening volume cinder-vol-c97d1067-6f88-46e5-b7a6-8f47c44d0fab (317eb2cf-88bc-4e24-bfd7-e4c70da05b76)
[ I |  9/15 09:30:58.851 | 87356 | 4.9 ] Setting metadata cache size to 500000 based on available system memory of 12 GiB
[ I |  9/15 09:30:58.856 | 87356 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/15 09:30:58.862 | 87383 | 4.9 ] Changed metadata cache configuration for volume 317eb2cf-88bc-4e24-bfd7-e4c70da05b76 to cache_ttl_ms: 0 negative_cache_ttl_ms: 0 enable_write_back_cache: false
[ I |  9/15 09:30:58.862 | 87356 | 4.9 ] Failed to invalidate inode: 38: Function not implemented
[ I |  9/15 09:30:58.889 | 87356 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:30:58.895 | 87378 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:31:01.796 | 87357 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/15 09:31:09.347 | 87379 | 4.9 ]  `-> suppressed previous message 1 time
[ W |  9/15 09:31:09.347 | 87379 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:31:24.128 | 87392 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:31:24.130 | 87378 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:31:45.734 | 87393 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:31:45.735 | 87379 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:32:18.084 | 87394 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:32:18.087 | 87380 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:33:08.089 | 87395 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:33:08.091 | 87380 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:34:07.533 | 87396 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:34:07.537 | 87381 | 4.9 ] Request 13001:1 (23) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=27: error_type: INVALID_STATE error_message: "CLIENT RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:35:04.602 | 87397 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:35:04.605 | 87381 | 4.9 ] Request 13001:1 (27) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=32: error_type: INVALID_STATE error_message: "CLIENT RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:36:05.355 | 87398 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:36:05.358 | 87378 | 4.9 ] Request 13001:1 (32) 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:37:07.034 | 87391 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:37:07.037 | 87379 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:38:06.849 | 87392 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:38:06.851 | 87380 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:39:03.956 | 87393 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:39:03.958 | 87381 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:40:05.897 | 87394 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:40:05.899 | 87378 | 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:41:04.883 | 87395 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:41:04.885 | 87379 | 4.9 ] Request 13001:1 (57) 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:42:05.097 | 87396 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:42:05.100 | 87381 | 4.9 ] Request 13001:1 (63) 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 RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:43:04.956 | 87397 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:43:04.958 | 87378 | 4.9 ] Request 13001:1 (68) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=73: error_type: INVALID_STATE error_message: "CLIENT RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:44:07.809 | 87398 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:44:07.812 | 87379 | 4.9 ] Request 13001:1 (73) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=79: error_type: INVALID_STATE error_message: "CLIENT RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 09:45:05.246 | 87391 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 09:45:05.248 | 87381 | 4.9 ] Request 13001:1 (79) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=84: error_type: INVALID_STATE error_message: "CLIENT RN62Dcm1-ORRO-Hyu2-fFvj-OGbDRfnnqIph does not support enabled feature FILE_FORMAT_V3, please update it"