Add one for --srcport as well and I think you'll be ok. Actually, since
my cluster traffic all goes over a separate switch I usually just allow
all traffic in/out of eth1.
Brian
Bret Palsson 2009-01-15 08:12:
>So it looks like iptables is what is stopping it from working. After
>disabli
It's part and parcel of the fs. If you want mainline linux,
goto http://kernel.org.
Bret Palsson wrote:
> Can I get the source for DLM 1.5.0 and build it on my other machines?
> If so where do I grab it?
>
> Thanks,
>
> Bret
>
> On Jan 14, 2009, at 4:28 PM, Sunil Mushran wrote:
>
>> I hate cut-pa
Can I get the source for DLM 1.5.0 and build it on my other machines?
If so where do I grab it?
Thanks,
Bret
On Jan 14, 2009, at 4:28 PM, Sunil Mushran wrote:
> I hate cut-paste's because I have no idea whether I can trust it
> or not. A misspelled 0 and 1 makes a whole world of difference.
>
o: Michael Moody
Cc: ocfs2-users@oss.oracle.com
Subject: Re: [Ocfs2-users] [Ocfs2-devel] Transport endpoint is not connected
while mounting
AFAIR, mount will typically will error out with something like "mountpoint
does not exist". It should.
Michael Moody wrote:
>
> I know i
AFAIR, mount will typically will error out with something like "mountpoint
does not exist". It should.
Michael Moody wrote:
>
> I know it sounds stupid,
>
> I had this error, and similar dmesg output when I simply didn’t have
> the mountpoint existing (in my case, I mount /dev/sdc1 to /mnt/www,
I hate cut-paste's because I have no idea whether I can trust it
or not. A misspelled 0 and 1 makes a whole world of difference.
But the following seems to indicate that the configuration is bad.
(3130,1):o2net_connect_expired:1659 ERROR: no connection established
with node 0 after 30.0 seconds,
I know it sounds stupid,
I had this error, and similar dmesg output when I simply didn't have the
mountpoint existing (in my case, I mount /dev/sdc1 to /mnt/www, and /mnt/www
didn't exist, I had the same output). It's worth checking at least, though I'm
sure you already have.
Michael
_
Output of Node 0 {
OCFS2 Node Manager 1.4.1 Tue Dec 16 19:18:05 PST 2008 (build
0f78045c75c0174e50e4cf0934bf9eae)
OCFS2 DLM 1.4.1 Tue Dec 16 19:18:05 PST 2008 (build
4ce8fae327880c466761f40fb7619490)
OCFS2 DLMFS 1.4.1 Tue Dec 16 19:18:05 PST 2008 (build
4ce8fae327880c466761f40fb7619490)
OCFS
What about the dmesg on node 1?
Now ideally we want the fs versions to be the same on all nodes.
However as we have not changed the protocol since 1.4.1, this
should still work.
Bret Palsson wrote:
> node 0 (and FS) OCFS2 1.4.1 2.6.18-92.1.22.el5xen
> node 1 OCFS 21.5 2.6.28-vs2.3.0.36.4
>
> Outp
node 0 (and FS) OCFS2 1.4.1 2.6.18-92.1.22.el5xen
node 1 OCFS 21.5 2.6.28-vs2.3.0.36.4
Output of Node 1 {
OCFS2 Node Manager 1.5.0
OCFS2 DLM 1.5.0
ocfs2: Registered cluster interface o2cb
OCFS2 DLMFS 1.5.0
OCFS2 User DLM kernel interface loaded
device eth0 entered promiscuous mode
OCFS2 1.5.0
}
On
versions? kernel and fs.
Bret Palsson wrote:
> Does anyone have any idea what to try next? Here are the steps I have
> taken and the problem: (I wanted to post my question on the first
> line before I explained the problem and what I have tried)
>
> --
>
> Node 0 has the file syste
11 matches
Mail list logo