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

Page title matches

Page text matches

  • ...e consisting of a short prefix combined with regularly incremented decimal node numbers (e.g., n0001, n0002, etc.) works well with an automated tool like ' * '''Collect syslogs in one place.''' In addition to collecting logs on a per node basis, collecting syslogs in one location lets an administrator monitor a s
    2 KB (378 words) - 06:10, 22 February 2010
  • For information about recovering from a node or network failure, see the following:
    414 bytes (51 words) - 10:35, 20 January 2011
  • ...ly power off the failed node. Otherwise, there is a chance that the "dead" node could wake up, start using the disk at the same time, and cause massive cor ...and MDT level. Lustre failover is to handle the failure of an MDS or OSS node as a whole which, in our experience, is not very common.
    4 KB (657 words) - 08:31, 22 February 2010
  • '''Can I use more than one interface of the same type on the same node?''' '''Can I use two or more different interconnects on the same node?'''
    2 KB (377 words) - 08:28, 22 February 2010
  • ...nitiator to request that file data is read from one location and stored in another. # '''3rd Party IO''' - A node requests through a lustre client that data can be read/written through a 3
    1 KB (210 words) - 14:12, 22 January 2010
  • node, run: node, run:
    5 KB (758 words) - 11:53, 20 January 2011
  • ...iguous set of fids, all fids from given sequence belong to single specific node ; '''fld''': persistent sequence to node mapping
    3 KB (382 words) - 14:09, 22 January 2010
  • |<strong>network type</strong>||TCP/IP||<strong>MGS node</strong>||10.2.0.1@tcp0 |<strong>block device</strong>||/dev/sdb||<strong>OSS 1 node</strong>||oss1
    5 KB (684 words) - 11:02, 22 February 2010
  • ...the consistency of these share modes and oplocks, you should use a single node to export CIFS. '''What is the typical MDS node configuration?'''
    6 KB (956 words) - 08:26, 22 February 2010
  • A node may have one or more link sets - these are a set of nids that # The nids in a link set will be made available though the LNET management node (probably the MGS) to allow dynamic server addition.
    4 KB (668 words) - 14:18, 22 January 2010
  • ...he Reduce node uses the HTTP protocol to retrieve Map results from the Map node protocol. The HTTP protocol is not a good choice for large data transfers b
    2 KB (362 words) - 12:00, 22 February 2010
  • ...then OSTs. Unmounting a block device causes Lustre to be shut down on that node. :a. Unmount the clients. On each client node, run:
    10 KB (1,542 words) - 10:23, 20 January 2011
  • ...er than the product of the total number of nodes and maximum processes per node. ...cs_per_node'' is the maximum number of cores (CPUs), on a single Catamount node. Portals must know this value to properly clean up various queues. LNET is
    3 KB (438 words) - 08:54, 22 February 2010
  • ...number of Lustre targets and, in case of a failure, the active/non-failed node takes over the Lustre targets of the failed nodes and makes them available ...nodes are equipped with a service processor allowing to shut down a failed node using IPMI. For other methods of fencing, refer to the RedHat Cluster docum
    16 KB (2,207 words) - 09:13, 20 December 2010
  • The Lustre™ node file system ''ldiskfs'' (based on ext3/ext4) is limited to an 8 TB maximum ...ct any data corruption introduced into the network between the application node and the disk drive in the Lustre storage system.
    4 KB (617 words) - 11:26, 10 September 2010
  • ...an also cause problems by, for example, making it difficult to debug multi-node issues or correlate logs, which depend on timestamps. We recommend that you ...re (new in Lustre 1.8), which consumes memory as it caches data on the OSS node.
    9 KB (1,347 words) - 10:17, 20 January 2011
  • *For each client node, create a lustre_root principal and generate keytab. *Install the keytab on the client node.
    10 KB (1,660 words) - 09:26, 12 April 2013
  • '''[[FAQ - Sizing|Sizing]]''' - File system, file, I/O request, OSS, and node limitations.
    1 KB (189 words) - 11:16, 22 February 2010
  • ;'''Migration''': moving file data from one set of OSTs to another ...ts get sent to it, it does locking and optionally can redirect a client to another server where data access will happen without further locking
    11 KB (1,647 words) - 14:22, 22 January 2010
  • ...ster failure || failover support to avoid any failure of a Lustre or Samba node stopping the whole cluster. ...|| all resources (like opened handles or locks) grabbed by a dead client node should be gracefully released, or other clients will be forbidden to access
    16 KB (2,220 words) - 13:14, 2 February 2010
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)