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

  • === Punch === punch(inode, start, end, version, flags)
    444 bytes (60 words) - 14:21, 22 January 2010
  • |+ Punch functionality use cases ...ers || optionally an inode version can be passed to the punch call and the punch will only take place if the inode, when locked has the version passed into
    1 KB (205 words) - 14:21, 22 January 2010
  • The architecture descriptions listed below provide information about Lustre architecture and design and are intended to help users better understand the conceptual ...information that is incomplete or obsolete and may not reflect the current architecture, features and functionality of Lustre.''
    9 KB (1,200 words) - 12:09, 20 January 2011
  • * ''Architecture.'' See [[Architecture - HSM and Cache]] |punch||Feature||The system can process a list of files moved to the backend stora
    2 KB (369 words) - 14:12, 22 January 2010
  • ...esponsible for copying-out candidate files to the HSM when possible (see [[Architecture - HSM Migration|HSM Migration]]). ...olicy limit is reached inside the filesystem, the space manager is used to punch as many objects as needed to fall short of the limit.
    5 KB (722 words) - 14:24, 22 January 2010
  • == SNS Architecture Overview == ...the parity stripe unit of the last full stripe after truncate. (two phase: punch, parity update)
    26 KB (3,768 words) - 14:23, 22 January 2010
  • This page describes use cases and high-level architecture for migrating files between Lustre and a HSM system. ## policy engine will provide the functionality of the [[Architecture - Space Manager|Space Manager]] and any other archive/release policies
    25 KB (3,874 words) - 14:12, 22 January 2010