Handling File System Errors
Jump to navigation
Jump to search
| Note: This page originated on the old Lustre wiki. It was identified as likely having value and was migrated to the new wiki. It is in the process of being reviewed/updated and may currently have content that is out of date. |
|---|
(Updated: Mar 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. In such cases, it may also be useful to run lfsck, a Lustre™-specific fsck tool that checks the coherency of a running Lustre file system as a whole.
A Lustre-specific version of e2fsprogs can be found at http://downloads.lustre.org/public/tools/e2fsprogs/. A quilt patchset of all changes to the vanilla e2fsprogs is available in e2fsprogs-{version}-patches.tgz.
For information about:
- Using e2fsck on a backing file system, see Section 27.1: Recovering from Errors or Corruption on a Backing File System in the Lustre Operations Manual.
- Running e2fsck+lfsck on a corrupted Lustre file system, see Section 27.2: Recovering from Corruption in the Lustre File System in the Lustre Operations Manual.
- Addressing orphaned objects, see Section 27.2.1: Working with Orphaned Objects in the Lustre Operations Manual.
For more information about lfsck, see Section 32.3: lfsck in the Lustre Operations Manual.