[Ocfs2-users] Problems mounting shared filesystem

Chris Clonch cclonch at gmail.com
Fri Mar 26 06:54:32 PDT 2010


Turns out the firewall was reenabled on nodes 1 and 3.  I'm guessing
this happened when we added the new NICs and it kicked off the
reconfigure on first boot...  Speculation though.

-Chris

On Tue, Mar 23, 2010 at 5:08 PM, Chris Clonch <cclonch at gmail.com> wrote:
> Rebooted using my working 2.6.18-164.11.1.el5 kernel.  Now I can get
> node1 active with the shared filesystems mounted but the other nodes
> refuse to mount them.  Enabled TCP tracing on the working node1.
> Running netcat from node2 to node1 (192.168.1.1) does not produce any
> output anywhere.
>
> I believe I'm having a routing issue; traceroute stumbles every so
> often.  I'm currently using tcpdump to sort out whats going on.
>
> Thanks,
> -Chris
>
>
>
> On Tue, Mar 23, 2010 at 3:07 PM, Chris Clonch <cclonch at gmail.com> wrote:
>> Thanks for the reply Sunil!  I thought it might be a network issue,
>> but when I enabled debug then ran netcat against it I could connect.
>> Firewall and SELinux are both disabled on all nodes.
>>
>> I went ahead and reran the ethernet for both sets of NIC to ensure the
>> old hub I was using was not a factor.  Now everything runs through an
>> enterprise-class switch.  Stats from netstat and ethtool look normal;
>> I did not view them prior to the changes.  I also pulled down the
>> latest updates from RHEL (did I mention these are RHEL5.4?), which
>> included kernel-2.6.18-164.15.1.el5.  Now the ocfs2_stackglue and
>> ocfs2_dlmfs modules are failing to load.
>>
>> -Chris
>>
>>
>> On Mon, Mar 22, 2010 at 4:52 PM, Sunil Mushran <sunil.mushran at oracle.com> wrote:
>>>
>>> The network connect is failing. Could be because of a firewall,
>>> or bad ip address, some switch issue.
>>>
>>> Mount the volume on node 2. Then enable tracing and
>>> tail messages file.
>>> # debugfs.ocfs2 -l TCP allow
>>> # tail -f /var/log/messages
>>>
>>> Then from node 4, ping node 2 using netcat.
>>> # nc -z 192.168.1.2 7777
>>>
>>> If it succeeds, then you should see:
>>> Connection to 192.168.1.2 7777 port [tcp/cbt] succeeded!
>>>
>>> Additionally, you will see a message on node 2 "attempt to connect
>>> from node...".
>>>
>>> If not, then look at your network setup.
>>>
>>> Remember to disable tracing on node 2.
>>> #debugfs.ocfs2 -l TCP off
>>>
>>> Sunil
>>
>



More information about the Ocfs2-users mailing list