[ I | 9/14 11:41:33.696 | 87465 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg [ I | 9/14 11:41:33.697 | 87465 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg [ I | 9/14 11:41:33.697 | 87465 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/71fb30fa62daab18a0dda8e1be030aac' to display the log. [ I | 9/14 11:41:33.696 | 87465 | 4.9 ] Reading configuration file: /etc/quobyte/client-cinder.cfg [ I | 9/14 11:41:33.697 | 87465 | 4.9 ] Reading configuration file: /etc/quobyte/client.cfg [ I | 9/14 11:41:33.697 | 87465 | 4.9 ] Quobyte logging to journald, you can use 'journalctl QUOBYTE_MOUNTPOINT=/opt/stack/data/cinder/mnt/71fb30fa62daab18a0dda8e1be030aac' to display the log. [ I | 9/14 11:41:33.700 | 87466 | 4.9 ] mount.quobyte 4.9 (1db25233e74) [ I | 9/14 11:41:33.700 | 87466 | 4.9 ] Client UUID: YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 [ I | 9/14 11:41:33.700 | 87466 | 4.9 ] Registry: osci02.corp.quobyte.com:7861 [ I | 9/14 11:41:33.700 | 87466 | 4.9 ] Volume: cinder-vol-cb183d08-7cd8-4d17-98c2-6cfbd2e98221 [ I | 9/14 11:41:33.700 | 87466 | 4.9 ] FUSE version: 316 [ I | 9/14 11:41:33.705 | 87466 | 4.9 ] Breakpad initialized (dumping to /root/.quobyte/minidumps) [ I | 9/14 11:41:33.729 | 87466 | 4.9 ] Setting total object cache size to 2508193792 bytes [ I | 9/14 11:41:33.729 | 87466 | 4.9 ] Using FUSE low-level API [ I | 9/14 11:41:33.730 | 87466 | 4.9 ] Caching of uid/gid to user/group name mappings is enabled [ I | 9/14 11:41:33.730 | 87466 | 4.9 ] Setting up sockets network client, connect timeout (s): 2 linger timeout (s): 1200 request timeout granularity (s): 10 [ I | 9/14 11:41:33.743 | 87492 | 4.9 ] HTTP server started on port 55000 [ I | 9/14 11:41:33.743 | 87466 | 4.9 ] Caching mappings from uid/gid to user/group name and group membership temporarily. [ I | 9/14 11:41:33.747 | 87466 | 4.9 ] Mount point /opt/stack/data/cinder/mnt/71fb30fa62daab18a0dda8e1be030aac established [ I | 9/14 11:41:33.747 | 87466 | 4.9 ] TimeSync is running and remote sync every 60 seconds [ I | 9/14 11:41:33.757 | 87466 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ I | 9/14 11:41:33.776 | 87466 | 4.9 ] `-> suppressed previous message 1 time [ I | 9/14 11:41:33.776 | 87466 | 4.9 ] Opening volume cinder-vol-cb183d08-7cd8-4d17-98c2-6cfbd2e98221 (c64aa66e-ce64-48a9-9ceb-1ce74fa7a336) [ I | 9/14 11:41:33.780 | 87466 | 4.9 ] Setting metadata cache size to 500000 based on available system memory of 12 GiB [ I | 9/14 11:41:33.788 | 87466 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ I | 9/14 11:41:33.795 | 87495 | 4.9 ] Changed metadata cache configuration for volume c64aa66e-ce64-48a9-9ceb-1ce74fa7a336 to cache_ttl_ms: 0 negative_cache_ttl_ms: 0 enable_write_back_cache: false [ I | 9/14 11:41:33.795 | 87466 | 4.9 ] Failed to invalidate inode: 38: Function not implemented [ I | 9/14 11:41:33.812 | 87466 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:41:33.818 | 87488 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:41:36.759 | 87467 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ I | 9/14 11:41:43.415 | 87489 | 4.9 ] `-> suppressed previous message 1 time [ W | 9/14 11:41:43.415 | 87489 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:41:58.266 | 87502 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:41:58.269 | 87488 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:42:19.990 | 87503 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:42:19.993 | 87489 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:42:53.284 | 87504 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:42:53.286 | 87491 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:43:43.914 | 87506 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:43:43.917 | 87491 | 4.9 ] Request 13001:1 (19) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=24: error_type: INVALID_STATE error_message: "CLIENT YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:44:46.811 | 87507 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:44:46.815 | 87488 | 4.9 ] Request 13001:1 (24) 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:45:44.168 | 87508 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:45:44.172 | 87488 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:46:45.602 | 87505 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:46:45.605 | 87489 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:47:47.318 | 87501 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:47:47.320 | 87490 | 4.9 ] Request 13001:1 (38) 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:48:45.693 | 87502 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:48:45.696 | 87490 | 4.9 ] Request 13001:1 (42) 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:49:44.270 | 87503 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:49:44.272 | 87488 | 4.9 ] Request 13001:1 (48) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=54: error_type: INVALID_STATE error_message: "CLIENT YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:50:44.401 | 87504 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:50:44.403 | 87490 | 4.9 ] Request 13001:1 (54) received error from registry-client:@10.10.41.20:7861 retrying on different server with call_id=59: error_type: INVALID_STATE error_message: "CLIENT YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:51:42.422 | 87506 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:51:42.424 | 87491 | 4.9 ] Request 13001:1 (59) 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:52:45.167 | 87507 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:52:45.169 | 87491 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:53:44.616 | 87508 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:53:44.618 | 87488 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:54:46.037 | 87505 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:54:46.039 | 87489 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it" [ I | 9/14 11:55:43.595 | 87501 | 4.9 ] Resolved Registry handle as: 10.10.41.20:7861 [ W | 9/14 11:55:43.597 | 87491 | 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 YDHNTTFD-kDmt-DMvv-4LJS-M1gLelux5Ne1 does not support enabled feature FILE_FORMAT_V3, please update it"