[ I |  9/15 02:27:28.865 | 87427 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/15 02:27:28.866 | 87427 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/15 02:27:28.866 | 87427 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/7c629199ab49257b69dd531aa063b9dd' to display the log.
[ I |  9/15 02:27:28.865 | 87427 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/15 02:27:28.866 | 87427 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/15 02:27:28.866 | 87427 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/7c629199ab49257b69dd531aa063b9dd' to display the log.
[ I |  9/15 02:27:28.870 | 87428 | 4.9 ] mount.quobyte 4.9 (1db25233e74)
[ I |  9/15 02:27:28.870 | 87428 | 4.9 ] Client UUID: nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt
[ I |  9/15 02:27:28.870 | 87428 | 4.9 ] Registry: osci02.corp.quobyte.com:7861
[ I |  9/15 02:27:28.870 | 87428 | 4.9 ] Volume: cinder-vol-a78161e9-4556-49e8-a317-da327e22da3e
[ I |  9/15 02:27:28.870 | 87428 | 4.9 ] FUSE version: 316
[ I |  9/15 02:27:28.874 | 87428 | 4.9 ] Breakpad initialized (dumping to /root/.quobyte/minidumps)
[ I |  9/15 02:27:28.900 | 87428 | 4.9 ] Setting total object cache size to 2508193792 bytes
[ I |  9/15 02:27:28.900 | 87428 | 4.9 ] Using FUSE low-level API
[ I |  9/15 02:27:28.900 | 87428 | 4.9 ] Caching of uid/gid to user/group name mappings is enabled
[ I |  9/15 02:27:28.901 | 87428 | 4.9 ] Setting up sockets network client, connect timeout (s): 2 linger timeout (s): 1200 request timeout granularity (s): 10
[ I |  9/15 02:27:28.915 | 87454 | 4.9 ] HTTP server started on port 55000
[ I |  9/15 02:27:28.915 | 87428 | 4.9 ] Caching mappings from uid/gid to user/group name and group membership temporarily.
[ I |  9/15 02:27:28.916 | 87428 | 4.9 ] Mount point /opt/stack/data/cinder/mnt/7c629199ab49257b69dd531aa063b9dd established
[ I |  9/15 02:27:28.916 | 87428 | 4.9 ] TimeSync is running and remote sync every 60 seconds
[ I |  9/15 02:27:28.928 | 87428 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/15 02:27:28.944 | 87428 | 4.9 ]  `-> suppressed previous message 1 time
[ I |  9/15 02:27:28.944 | 87428 | 4.9 ] Opening volume cinder-vol-a78161e9-4556-49e8-a317-da327e22da3e (f442472a-48c4-4a72-8b6b-199c7052f58f)
[ I |  9/15 02:27:28.947 | 87428 | 4.9 ] Setting metadata cache size to 500000 based on available system memory of 12 GiB
[ I |  9/15 02:27:28.952 | 87428 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/15 02:27:28.959 | 87459 | 4.9 ] Changed metadata cache configuration for volume f442472a-48c4-4a72-8b6b-199c7052f58f to cache_ttl_ms: 0 negative_cache_ttl_ms: 0 enable_write_back_cache: false
[ I |  9/15 02:27:28.960 | 87428 | 4.9 ] Failed to invalidate inode: 38: Function not implemented
[ I |  9/15 02:27:28.976 | 87428 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:27:28.983 | 87450 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:27:31.945 | 87431 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/15 02:27:39.439 | 87451 | 4.9 ]  `-> suppressed previous message 1 time
[ W |  9/15 02:27:39.439 | 87451 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:27:54.638 | 87465 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:27:54.642 | 87450 | 4.9 ] Request 13001:1 (12) 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:28:16.972 | 87466 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:28:16.974 | 87452 | 4.9 ] Request 13001:1 (14) 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:28:48.906 | 87468 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:28:48.911 | 87453 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:29:37.245 | 87470 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:29:37.249 | 87453 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:30:38.080 | 87463 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:30:38.083 | 87453 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:31:37.988 | 87467 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:31:37.991 | 87450 | 4.9 ] Request 13001:1 (28) 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:32:35.859 | 87469 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:32:35.861 | 87450 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:33:33.731 | 87464 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:33:33.735 | 87451 | 4.9 ] Request 13001:1 (37) 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:34:35.387 | 87465 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:34:35.390 | 87453 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:35:36.680 | 87466 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:35:36.683 | 87453 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:36:35.449 | 87468 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:36:35.451 | 87450 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:37:34.083 | 87470 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:37:34.085 | 87451 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:38:33.992 | 87463 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:38:33.994 | 87452 | 4.9 ] Request 13001:1 (62) 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/15 02:39:34.144 | 87467 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/15 02:39:34.148 | 87453 | 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 nclxWLrl-Swyt-moKX-apw0-0WUCKnHki2Zt does not support enabled feature FILE_FORMAT_V3, please update it"