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.

Difference between revisions of "Handling File System Errors"

From Obsolete Lustre Wiki
Jump to navigationJump to search
Line 7: Line 7:
 
* Running e2fsck+lfsck on a corrupted Lustre file system
 
* Running e2fsck+lfsck on a corrupted Lustre file system
  
For more information about ''lfsck'', see [http://wiki.lustre.org/manual/LustreManual18_HTML/UserUtilitiesMan1_HTML.html#50532398_pgfId-1292867 Section 27.2: ''lfsck''] in the [[Lustre Documentation|''Lustre Operations Manual'']].
+
For more information about ''lfsck'', see [http://wiki.lustre.org/manual/LustreManual18_HTML/UserUtilitiesMan1_HTML.html#50638894_91700 Section 27.2: ''lfsck''] in the [[Lustre Documentation|''Lustre Operations Manual'']].
  
 
''(Updated 01/10)''
 
''(Updated 01/10)''

Revision as of 21:18, 18 February 2010

From time to time, usually due to catastrophic disk / RAID failures, it may be necessary to repair the backing file system of an OST or MDT to correct file system errors. This is done using a special version of the e2fsck tool. It may also be useful to run lfsck in such cases. This is a Lustre™-specific tool that checks the coherency of a running Lustre file system as a whole.

For information on the following topics, see Fsck Support.

  • Obtaining e2fsck support for Lustre
  • Using e2fsck on a backing file system
  • Running e2fsck+lfsck on a corrupted Lustre file system

For more information about lfsck, see Section 27.2: lfsck in the Lustre Operations Manual.

(Updated 01/10)