Got it working. The firewall was blocking lustre traffic. :( After disabling
it, it works.
Thanks all for the help!
On Sat, Jan 16, 2010 at 9:57 AM, Dusty Marks wrote:
> I've posted my /var/log/messages here before, but here it is again:
>
>
> --- /var/log/me
I've posted my /var/log/messages here before, but here it is again:
--- /var/log/messages
---
Jan 14 22:41:05 oss kernel: Lustre: OBD class driver, http://www.lustre.org/
Jan 14 22:41:05 oss kernel: Lustre
Wojciech Turek wrote:
> Hi,
>
> Could you please post output of the 'lctl list_nids' command on OSS
> system and on MDS system. This will show us which network was
> configured to work with lustre.
>
> Regarding entries in the modprobe.conf, they tell lnet module which
> NIC or multiple NICs will
Dusty Marks wrote:
> Yes. MDS and OSS can be pinged using the normal ping command. (ping
> 192.168.0.2 and ping 192.168.0.3)
>
> I am not sure what you want me to post for syslog? I always thought
> syslog was just a config file telling an application where to append
> certain error message
sys
Yes. MDS and OSS can be pinged using the normal ping command. (ping
192.168.0.2 and ping 192.168.0.3)
I am not sure what you want me to post for syslog? I always thought syslog
was just a config file telling an application where to append certain error
messages.
thanks
dusty
On Fri, Jan 15, 2010
Could you also post here syslog messages from the OSS ?
2010/1/16 Wojciech Turek :
> Can you check if you can ping MDS and OSS using normal ping command?
>
>
> 2010/1/16 Dusty Marks :
>> the output of ltcl list_nids on the oss is
>>
>> [r...@oss ~]# lctl list_nids
>> 192.168@tcp
>>
>> and from
Can you check if you can ping MDS and OSS using normal ping command?
2010/1/16 Dusty Marks :
> the output of ltcl list_nids on the oss is
>
> [r...@oss ~]# lctl list_nids
> 192.168@tcp
>
> and from the mds
>
> [r...@mds ~]# lctl list_nids
> 192.168@tcp
>
> Thanks,
> Dusty
>
> On Fri, Jan
the output of ltcl list_nids on the oss is
[r...@oss ~]# lctl list_nids
192.168@tcp
and from the mds
[r...@mds ~]# lctl list_nids
192.168@tcp
Thanks,
Dusty
On Fri, Jan 15, 2010 at 5:39 PM, Wojciech Turek wrote:
> Hi,
>
> Could you please post output of the 'lctl list_nids' command on
Hi,
Could you please post output of the 'lctl list_nids' command on OSS
system and on MDS system. This will show us which network was
configured to work with lustre.
Regarding entries in the modprobe.conf, they tell lnet module which
NIC or multiple NICs will be configured to work with lustre. If
I did some googling and i found the command lctl ping. So i went on the oss
and typed in "lctl ping 192.168@tcp". This errored out with an I/O
error.
It is quite obvious that i've simply misconfigured the network. Could
someone explain how to properly configure it?
I don't understand what the
On 2010-01-15, at 00:21, Arden Wiebe wrote:
> Your mount command is wrong - try this format.
>
> mount -t lustre 192.168@tcp0:/ioio /mnt/ioio
>
> So by substitution for supplied your mount line should
> read:
>
> mount -t datafs 192.168@tcp0:/datafs /mnt/datafs
No, that isn't correct. Yo
--- On Thu, 1/14/10, Arden Wiebe wrote:
> DM:
>
> Your mount command is wrong - try this format.
>
> mount -t lustre 192.168@tcp0:/ioio /mnt/ioio
>
> > [r...@oss ~]# mkfs.lustre --fsname=datafs --ost --
> > mgsnode=192.168@tcp0 [r...@oss ~]# mount -t lustre
> /dev/lustre/
> > OST /lus
12 matches
Mail list logo
