Re: [lustre-discuss] lustre mount in heterogeneous net environment-update

[Jeff Johnson]

Greetings Megan,

One scenario that could cause this is if your appliance-style Lustre MDS is
a high-availability server pair and your mount command is not declaring
both NIDs in the mount command *and* the MGS and MDT resources happen to be
presently residing on the MDS server you are not declaring in your mount
command.

If it is high-availability and the IPs of those servers is A.B.C.D and
A.B.C.E then make sure your command command looks something like:

mount -t lustre A.B.C.D@tcp:A.B.C.E@tcp:/somefsname /localmountpoint

That way the client will be looking for the MGS in all of the places it
*could* be located.

Just one possibility of what may be the cause. Certainly easier and less
painful than a lower level version compatibility issue.

—Jeff

On Wed, Feb 28, 2018 at 13:36 Ms. Megan Larko  wrote:

> Greetings List!
>
> We have been continuing to dissect our LNet environment between our
> lustre-2.7.0 clients and the lustre-2.7.18 servers.  We have moved from the
> client node to the LNet server which bridges the InfiniBand (IB) and
> ethernet networks.   As a test, we attempted to mount the ethernet Lustre
> storage from the LNet hopefully taking the IB out of the equation to limit
> the scope of our debugging.
>
> On the LNet router the attempted mount of Lustre storage fails.   The LNet
> command line error on the test LNet client is exactly the same as the
> original client result:
> mount A.B.C.D@tcp0:/lustre at /mnt/lustre failed: Input/output error  Is
> the MGS running?
>
> On the lustre servers, both the MGS/MDS and OSS we can see the error via
> dmesg:
> LNet: There was an unexpected network error while writing to C.D.E.F:  -110
>
> and we see the periodic (~ every 10 to 20 minutes) in dmesg on MGS/MDS:
> Lustre: MGS: Client  (at C.D.E.F@tcp) reconnecting
>
> The "lctl pings" in various directions are still successful.
>
> So, forget the end lustre client, we are not yet getting from MGS/MDS
> sucessfully to the LNet router.
> We have been looking at the contents of /sys/module/lustre.conf and we are
> not seeing any differences in set values between the LNet router we are
> using as a test Lustre client and the Lustre MGS/MDS server.
>
> As much as I'd _love_ to go to Lustre-2.10.x, we are dealing with both
> "appliance" style Lustre storage systems and clients tied to specific
> versions of the linux kernel (for reasons other than Lustre).
>
> Is there a key parameter which I could still be overlooking?
>
> Cheers,
> megan
> ___
> lustre-discuss mailing list
> lustre-discuss@lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
-- 
--
Jeff Johnson
Co-Founder
Aeon Computing

jeff.john...@aeoncomputing.com
www.aeoncomputing.com
t: 858-412-3810 x1001   f: 858-412-3845
m: 619-204-9061

4170 Morena Boulevard, Suite D - San Diego, CA 92117

High-Performance Computing / Lustre Filesystems / Scale-out Storage
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

[lustre-discuss] Closing Today - Lustre Usage Survey

[OpenSFS Administration]

Hello Lustre Community, 

 

There are still a few hours remaining to submit your response to the Lustre
Usage Survey! Since the survey closes today, February 28th, we hope you'll
take a few minutes to provide your feedback in order to help us identify
Lustre usage trends and assist with future planning on releases. 

 

The survey only takes a few minutes to complete and can be accessed at
https://www.surveymonkey.com/r/ZVZ2663. Note that all questions are
optional, so it is ok to submit a partially completed survey if you prefer
not to disclose some information. The results of the survey will be shared
at LUG 2018. 

 

Thanks for your participation, 

OpenSFS Administration

__

OpenSFS Administration

3855 SW 153rd Drive Beaverton, OR 97003 USA

Phone: +1 503-619-0561 | Fax: +1 503-644-6708

Twitter:
 @OpenSFS 

Email:   ad...@opensfs.org | Website:
 www.opensfs.org 

 

___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] Lustre client 2.10.3 with 2.1 server

[Raj Ayyampalayam]

Yes, this is a CStor 1500 unit originally supplied by Xyratek.
Thanks for your recommendation.

-Raj

On Tue, Feb 27, 2018 at 8:05 PM Dilger, Andreas 
wrote:

> On Feb 27, 2018, at 16:19, Raj Ayyampalayam  wrote:
> >
> > We are using a lustre 2.1 server with 2.5 client.
> >
> > Can the latest 2.10.3 client can be used with the 2.1 server?
> > I figured I would ask the list before I start installing the client on a
> test node.
>
> I don't believe this is possible, due to changes in the protocol.  In any
> case, we haven't tested the 2.1 code in many years.
>
> Very likely your "2.1" server is really a vendor port with thousands of
> patches, so you might consider to ask the vendor, in case they've tested
> this.  If not, then I'd strongly recommend to upgrade to a newer release on
> the server.
>
> Cheers, Andreas
> --
> Andreas Dilger
> Lustre Principal Architect
> Intel Corporation
>
>
>
>
>
>
>
>
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org