此内容没有您所选择的语言版本。

Chapter 3. Known Issues


This chapter provides a list of known issues at the time of release.
  • In a gluster cluster with more than three nodes, if one or more nodes are down, but at least three nodes are up, heketi intermittently fails to create new replica 3 volumes, even if the healthy nodes have sufficient space available.
    To workaround this issue, execute the following commend on the unavailable nodes, which makes heketi volume creation 100% reliable:
    # heketi-cli node disable <node-id>
    Copy to Clipboard Toggle word wrap
    After the nodes are available again, execute the following command to let heketi take this node into account again when creating volumes:
    heketi-cli node enable <node-id>
    Copy to Clipboard Toggle word wrap
  • Volumes that were created using Container-Native Storage 3.5 or previous do not have the GID stored in heketi database. Hence, when a volume expansion is performed, new bricks do not get the group ID set on them which might lead to I/O errors.
  • The following two lines might be repeatedly logged in the rhgs-server-docker container/gluster container logs.
    [MSGID: 106006] [glusterd-svc-mgmt.c:323:glusterd_svc_common_rpc_notify] 0-management: nfs has disconnected from glusterd.
    [socket.c:701:__socket_rwv] 0-nfs: readv on /var/run/gluster/1ab7d02f7e575c09b793c68ec2a478a5.socket failed (Invalid argument)
    Copy to Clipboard Toggle word wrap
    These logs are added as glusterd is unable to start the NFS service. There is no functional impact as NFS export is not supported in Containerized Red Hat Gluster Storage.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat