WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Search results

From Obsolete Lustre Wiki
Jump to navigationJump to search
  • 1. Configure client nodes: *For each client node, create a lustre_root principal and generate keytab.
    10 KB (1,660 words) - 09:26, 12 April 2013
  • This document describes an architecture for client, server, network, and storage interoperability during migration from 1.6-ba ; '''OLD.x''' : a release in b1_6 line containing client that is able to interact with a NEW.0 md server. (Tentatively 1.8.)
    34 KB (5,038 words) - 00:19, 4 October 2012
  • ...the OST service on an OSS processes I/O requests and the AST service on a client processes notifications of lock conflicts. ...ster configuration is stored on the MGS in a special configuration llog. A client may access it via an llog API working over ptlrpc;
    51 KB (8,203 words) - 06:28, 11 April 2010
  • Client support for unpatched kernels: ...problem when decoding lsm because the # of OSTs was over tgt count at the client side.
    188 KB (28,583 words) - 05:09, 24 July 2013
  • Client support for unpatched kernels: (see [[Patchless Client]]) Client support for unpatched kernels:
    166 KB (24,668 words) - 06:38, 22 February 2010