[ I |  9/14 18:58:51.908 | 87420 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/14 18:58:51.909 | 87420 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/14 18:58:51.910 | 87420 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/de0f7469574df6222d0ad22391b11c58' to display the log.
[ I |  9/14 18:58:51.908 | 87420 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg
[ I |  9/14 18:58:51.909 | 87420 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg
[ I |  9/14 18:58:51.910 | 87420 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/de0f7469574df6222d0ad22391b11c58' to display the log.
[ I |  9/14 18:58:51.912 | 87421 | 4.9 ] mount.quobyte 4.9 (1db25233e74)
[ I |  9/14 18:58:51.912 | 87421 | 4.9 ] Client UUID: nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD
[ I |  9/14 18:58:51.913 | 87421 | 4.9 ] Registry: osci02.corp.quobyte.com:7861
[ I |  9/14 18:58:51.913 | 87421 | 4.9 ] Volume: cinder-vol-d877335c-ee54-43cc-a580-8c988a1c5c6a
[ I |  9/14 18:58:51.913 | 87421 | 4.9 ] FUSE version: 316
[ I |  9/14 18:58:51.918 | 87421 | 4.9 ] Breakpad initialized (dumping to /root/.quobyte/minidumps)
[ I |  9/14 18:58:51.944 | 87421 | 4.9 ] Setting total object cache size to 2508193792 bytes
[ I |  9/14 18:58:51.944 | 87421 | 4.9 ] Using FUSE low-level API
[ I |  9/14 18:58:51.944 | 87421 | 4.9 ] Caching of uid/gid to user/group name mappings is enabled
[ I |  9/14 18:58:51.945 | 87421 | 4.9 ] Setting up sockets network client, connect timeout (s): 2 linger timeout (s): 1200 request timeout granularity (s): 10
[ I |  9/14 18:58:51.959 | 87447 | 4.9 ] HTTP server started on port 55000
[ I |  9/14 18:58:51.959 | 87421 | 4.9 ] Caching mappings from uid/gid to user/group name and group membership temporarily.
[ I |  9/14 18:58:51.963 | 87421 | 4.9 ] Mount point /opt/stack/data/cinder/mnt/de0f7469574df6222d0ad22391b11c58 established
[ I |  9/14 18:58:51.963 | 87421 | 4.9 ] TimeSync is running and remote sync every 60 seconds
[ I |  9/14 18:58:51.976 | 87421 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 18:58:51.995 | 87421 | 4.9 ]  `-> suppressed previous message 1 time
[ I |  9/14 18:58:51.995 | 87421 | 4.9 ] Opening volume cinder-vol-d877335c-ee54-43cc-a580-8c988a1c5c6a (cc00fa95-a80f-4a8e-bf8c-4c8b0775d041)
[ I |  9/14 18:58:51.998 | 87421 | 4.9 ] Setting metadata cache size to 500000 based on available system memory of 12 GiB
[ I |  9/14 18:58:52.005 | 87421 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 18:58:52.012 | 87452 | 4.9 ] Changed metadata cache configuration for volume cc00fa95-a80f-4a8e-bf8c-4c8b0775d041 to cache_ttl_ms: 0 negative_cache_ttl_ms: 0 enable_write_back_cache: false
[ I |  9/14 18:58:52.012 | 87421 | 4.9 ] Failed to invalidate inode: 38: Function not implemented
[ I |  9/14 18:58:52.026 | 87421 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:58:52.030 | 87443 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:58:54.980 | 87422 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ I |  9/14 18:59:01.683 | 87444 | 4.9 ]  `-> suppressed previous message 1 time
[ W |  9/14 18:59:01.683 | 87444 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:59:16.840 | 87458 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:59:16.841 | 87443 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 18:59:38.887 | 87460 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 18:59:38.889 | 87444 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:00:12.245 | 87463 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:00:12.252 | 87446 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:00:59.836 | 87457 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:00:59.841 | 87446 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:02:01.950 | 87459 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:02:01.952 | 87446 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:03:00.582 | 87461 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:03:00.585 | 87444 | 4.9 ] Request 13001:1 (29) 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:04:02.434 | 87462 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:04:02.436 | 87444 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:05:02.725 | 87456 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:05:02.728 | 87445 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:06:03.416 | 87458 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:06:03.419 | 87446 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:07:00.873 | 87460 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:07:00.876 | 87446 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:08:03.321 | 87463 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:08:03.322 | 87443 | 4.9 ] Request 13001:1 (52) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=56: error_type: INVALID_STATE error_message: "CLIENT nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:09:03.039 | 87457 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:09:03.042 | 87443 | 4.9 ] Request 13001:1 (56) 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:10:00.780 | 87459 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:10:00.782 | 87445 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:11:03.058 | 87461 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:11:03.060 | 87446 | 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 nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it" 
[ I |  9/14 19:12:03.443 | 87462 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861
[ W |  9/14 19:12:03.446 | 87443 | 4.9 ] Request 13001:1 (72) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=76: error_type: INVALID_STATE error_message: "CLIENT nJ4iDGVA-epaP-a3aa-rw2L-tlOh0YpRZ9AD does not support enabled feature FILE_FORMAT_V3, please update it"