搜索

4.2. GFS2 File System Hangs and Requires Reboot of One Node

download PDF
If your GFS2 file system hangs and does not return commands run against it, but rebooting one specific node returns the system to normal, this may be indicative of a locking problem or bug. Should this occur, gather the following data:
  • The GFS2 lock dump for the file system on each node:
    cat /sys/kernel/debug/gfs2/fsname/glocks >glocks.fsname.nodename
  • The DLM lock dump for the file system on each node: You can get this information with the dlm_tool:
    dlm_tool lockdebug -sv lsname.
    
    In this command, lsname is the lockspace name used by DLM for the file system in question. You can find this value in the output from the group_tool command.
  • The output from the sysrq -t command.
  • The contents of the /var/log/messages file.
Once you have gathered that data, you can open a ticket with Red Hat Support and provide the data you have collected.
Red Hat logoGithubRedditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

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

让开源更具包容性

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

關於紅帽

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

© 2024 Red Hat, Inc.