[Lustre-discuss] Fw: Re: Unable to activate OST

[Andreas Dilger]

On 2010-01-15, at 00:21, Arden Wiebe wrote:
> Your mount command is wrong - try this format.
>
> mount -t lustre 192.168.0.7 at tcp0:/ioio /mnt/ioio
>
> So by substitution for supplied your mount line should
> read:
>
> mount -t datafs 192.168.0.2 at tcp0:/datafs /mnt/datafs

No, that isn't correct.  You are showing the mount command for a
client.  It is the OST that is failing to mount, likely because
the network is not configured correctly, and the OST needs to
contact the MGS node always on the first mount in order to join
the filesystem.

> Enjoy the required reading and testing.  I found by
> naming things uniquely helped me clarify what was actually
> required.  Try calling your filesystem "Dusty" or
> "Mark" and that should make things clearer for you.
>
> --- On Thu, 1/14/10, Andreas Dilger <adilger at sun.com> wrote:
>> On 2010-01-14, at 23:51, Dusty Marks wrote:
>>> You are correct, there is information in messages.  Following are  
>>> the
>>> entries related the lustre. The line that says 192.168.0.2 at tcp is
>>> unreachable makes sense, but what exactly is the problem? I entered
>>> the line "options lnet networks=tcp" in modprobe.conf on the oss and
>>> mds. The only difference was, i entered that line AFTER i setup
>>> lustre on the OSS. Could that be the problem? I don't see why that
>>> would be the problem, as the oss is trying to reach the MDS/MGS,
>>> which is 192.168.0.2.
>>>
>>> ---------------------------------------
>>> Jan 14 22:41:07 oss kernel: Lustre: 2846:0:(linux-tcpip.c:
>>> 688:libcfs_sock_connect()) Error -113 connecting 0.0.0.0/1023 ->
>>> 192.168.0.2/988
>>> Jan 14 22:41:07 oss kernel: Lustre: 2846:0:(acceptor.c:
>>> 95:lnet_connect_console_error()) Connection to 192.168.0.2 at tcp at
>>> host 192.168.0.2 was unreachable: the network or that node may be
>>> down, or Lustre may be misconfigured.
>>
>>
>> Please read the chapter in the manual about network configuration.  I
>> suspect the .0.2 network is not your eth0 network interface, and your
>> modprobe.conf needs to be fixed.


Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.