[Debian-ha-maintainers] Bug#1007141: BUG Report - OCFS2 Hangs when mount volume in second node

Dayvison sathlerds at gmail.com
Fri Mar 11 21:45:32 GMT 2022


Package: ocfs2-tools
Version: 8.7.1 and 8.6.6

Hi, I'm sending this email to report a problem:

OCFS2 filesystem with more than 1 node is not working with Debian 11 with 5.13, 5.15 and newer kernels.

OK, what's the problem behavior? Answer: When you mount ocfs2 on the second node with the "mount" command, the second node is stuck and unresponsive at the prompt, when viewing /var/log/syslog, there are several error messages in /var/log/syslog and no mounting the ocfs volume on the second node.

The ocfs2-tools that is in Debian 11 is version 8.6.6 (debian stable) and something changed in kernel 5.13 and 5.15 that stopped OCFS2 working when mounting the volume on the second node onwards.

When using the 8.7.1 version (available from debian testing) of ocfs-tools on the 5.13 and 5.15 kernels, the filesystem worked correctly again on the second node.

But in kernel 5.17 versions 8.6.6 and 8.7.1 no longer work.

So I see two problems:
1 - Version 8.6.6 of ocfs2-tools is no longer sufficient for kernel 5.13 and 5.15 from linux repository and will need to be replaced soon by version 8.7.1;
2 - Version 8.7.1 is enough to work on 5.13 and 5.15 kernels, however, it no longer works on 5.17 kernel and the ocfs2-tools package needs to be corrected for a new version of this kernel or other newer versions.

How to reproduce the problem:
1 - Configure the ocfs2 cluster and format the volume as ocfs2;
2 - mount the volume with the "mount" command on the first node
3 - mount the volume with the "mount" command on the second node"
4 - At this moment, the second node will have no response and messages in the syslog of failures, and the client will be stuck waiting for the assembly, which does not happen.

Tested environment:
System: Debian 11 64bit

Tested kernels to help developers:

4.9.0-13-amd64 + ocfs2-tools 8.6.6 (stable) = works
4.9.0-13-amd64 + ocfs2-tools 8.7.1 (sid) = works

5.10.6-1 + ocfs2-tools 8.6.6 (stable) = works
5.10.6-1 + ocfs2-tools 8.7.1 (sid) = works

5.10.0-11-amd64 + ocfs2-tools 8.6.6 (stable) = DOES NOT WORK
5.10.0-11-amd64 + ocfs2-tools 8.7.1 (sid) = works

5.13.19-4 + ocfs2-tools 8.6.6 (stable) = DOES NOT WORK
5.13.19-4 + ocfs2-tools 8.7.1 (sid) = works

5.14.0-0.bpo.2-amd64 + ocfs2-tools 8.7.1 (sid) = DOES NOT WORK

5.15.0-0.bpo.3-amd64 + ocfs2-tools 8.6.6 (stable) = DOES NOT WORK
5.15.0-0.bpo.3-amd64 + ocfs2-tools 8.7.1 (sid) = DOES NOT WORK

5.15.19-2 + ocfs2-tools 8.6.6 (stable) = DOES NOT WORK
5.15.19-2 + ocfs2-tools 8.7.1 (sid) = DOES NOT WORK

5.17-rc5-amd64 + ocfs2-tools 8.6.6 (stable) = DOES NOT WORK
5.17-rc5-amd64 + ocfs2-tools 8.7.1 (sid) = DOES NOT WORK

Hope it helps to find the problem. It would be interesting to report this to the OCFS2 developers, I don't know how to do this. If anyone knows and can help with this, I would be grateful.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-ha-maintainers/attachments/20220311/9c4070e6/attachment.htm>


More information about the Debian-ha-maintainers mailing list