Fsck Support - Revision history

Docadmin: Redirected page to Handling File System Errors

2010-03-27T19:50:18Z

Redirected page to Handling File System Errors

← Older revision		Revision as of 12:50, 27 March 2010
Line 1:		Line 1:
			#REDIRECT [[Handling_File_System_Errors]]
	<small>''(Updated: Oct 2009)''</small>		<small>''(Updated: Oct 2009)''</small>
	__TOC__		__TOC__

Sbarthel at 15:34, 22 February 2010

2010-02-22T15:34:06Z

← Older revision		Revision as of 08:34, 22 February 2010
Line 1:		Line 1:
	''(Updated: Oct 2009)''		<small>''(Updated: Oct 2009)''</small>

	__TOC__		__TOC__
	To support more advanced features of Lustre™, such as FIDs or multi-mount protection (MMP) support, you will need a Lustre-specific version of ''e2fsprogs'', which can be found at [http://downloads.lustre.org/public/tools/e2fsprogs/ http://downloads.lustre.org/public/tools/e2fsprogs/].		To support more advanced features of Lustre™, such as FIDs or multi-mount protection (MMP) support, you will need a Lustre-specific version of ''e2fsprogs'', which can be found at [http://downloads.lustre.org/public/tools/e2fsprogs/ http://downloads.lustre.org/public/tools/e2fsprogs/].

Sbarthel at 05:24, 22 February 2010

2010-02-22T05:24:54Z

← Older revision		Revision as of 22:24, 21 February 2010
Line 1:		Line 1:
			''(Updated: Oct 2009)''

	__TOC__		__TOC__
	To support more advanced features of Lustre™, such as FIDs or multi-mount protection (MMP) support, you will need a Lustre-specific version of ''e2fsprogs'', which can be found at [http://downloads.lustre.org/public/tools/e2fsprogs/ http://downloads.lustre.org/public/tools/e2fsprogs/].		To support more advanced features of Lustre™, such as FIDs or multi-mount protection (MMP) support, you will need a Lustre-specific version of ''e2fsprogs'', which can be found at [http://downloads.lustre.org/public/tools/e2fsprogs/ http://downloads.lustre.org/public/tools/e2fsprogs/].
Line 86:		Line 88:

	To fix inodes with duplicate objects, using ''lfsck'' with the ''-c'' option copies the duplicate object to a new object and assign it to one of the files. One of the files will be OK, and one will likely contain garbage, but ''lfsck'' cannot tell by itself which one is correct.		To fix inodes with duplicate objects, using ''lfsck'' with the ''-c'' option copies the duplicate object to a new object and assign it to one of the files. One of the files will be OK, and one will likely contain garbage, but ''lfsck'' cannot tell by itself which one is correct.

	~~''(Update 10/09)''~~

Docadmin at 23:08, 10 February 2010

2010-02-10T23:08:33Z

← Older revision		Revision as of 16:08, 10 February 2010
Line 86:		Line 86:

	To fix inodes with duplicate objects, using ''lfsck'' with the ''-c'' option copies the duplicate object to a new object and assign it to one of the files. One of the files will be OK, and one will likely contain garbage, but ''lfsck'' cannot tell by itself which one is correct.		To fix inodes with duplicate objects, using ''lfsck'' with the ''-c'' option copies the duplicate object to a new object and assign it to one of the files. One of the files will be OK, and one will likely contain garbage, but ''lfsck'' cannot tell by itself which one is correct.

			''(Update 10/09)''

Docadmin: /* Obtaining e2fsck Support for Lustre™ */

2009-12-17T20:19:44Z

Obtaining e2fsck Support for Lustre™

← Older revision		Revision as of 13:19, 17 December 2009
Line 1:		Line 1:
	~~== Obtaining ''e2fsck'' Support for Lustre™ ==~~		__TOC__

	To support more advanced features of Lustre™, such as FIDs or multi-mount protection (MMP) support, you will need a Lustre-specific version of ''e2fsprogs'', which can be found at [http://downloads.lustre.org/public/tools/e2fsprogs/ http://downloads.lustre.org/public/tools/e2fsprogs/].		To support more advanced features of Lustre™, such as FIDs or multi-mount protection (MMP) support, you will need a Lustre-specific version of ''e2fsprogs'', which can be found at [http://downloads.lustre.org/public/tools/e2fsprogs/ http://downloads.lustre.org/public/tools/e2fsprogs/].

Docadmin: Protected "Fsck Support" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2009-12-16T17:56:04Z

Protected "Fsck Support" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 10:56, 16 December 2009
(No difference)

Docadmin at 17:55, 16 December 2009

2009-12-16T17:55:53Z

← Older revision		Revision as of 10:55, 16 December 2009
Line 1:		Line 1:
	== Obtaining ''e2fsck'' Support for ~~Lustre~~ ==		== Obtaining ''e2fsck'' Support for Lustre™ ==

	To support more advanced features of ~~Lustre~~, such as FIDs or multi-mount protection (MMP) support, you will need a Lustre-specific version of ''e2fsprogs'', which can be found at [http://downloads.lustre.org/public/tools/e2fsprogs/ http://downloads.lustre.org/public/tools/e2fsprogs/].		To support more advanced features of Lustre™, such as FIDs or multi-mount protection (MMP) support, you will need a Lustre-specific version of ''e2fsprogs'', which can be found at [http://downloads.lustre.org/public/tools/e2fsprogs/ http://downloads.lustre.org/public/tools/e2fsprogs/].

	A quilt patchset of all changes to the vanilla e2fsprogs is available in ''e2fsprogs-{version}-patches.tgz''.		A quilt patchset of all changes to the vanilla e2fsprogs is available in ''e2fsprogs-{version}-patches.tgz''.

Docadmin: /* Using e2fsck on a Backing File System */

2009-10-07T21:42:59Z

Using e2fsck on a Backing File System

← Older revision		Revision as of 14:42, 7 October 2009
Line 24:		Line 24:
	This will cause the journal to be recovered.		This will cause the journal to be recovered.

	''e2fsck'' works well when fixing file system corruption (better than similar file system recovery tools and a primary reason why ext3 was chosen over other file systems for Lustre). However, it is often useful to identify the type of damage that has occurred so an ext3 expert can make intelligent decisions about what needs fixing, in place of ''e2fsck''. ~~[[Sun support is available for such situations.]]~~		''e2fsck'' works well when fixing file system corruption (better than similar file system recovery tools and a primary reason why ext3 was chosen over other file systems for Lustre). However, it is often useful to identify the type of damage that has occurred so an ext3 expert can make intelligent decisions about what needs fixing, in place of ''e2fsck''.

	<pre>		<pre>
Line 74:		Line 74:
	# Multiple inodes reference the same objects. This can happen if there was corruption on the MDS, or if the MDS storage is cached and loses some but not all writes.		# Multiple inodes reference the same objects. This can happen if there was corruption on the MDS, or if the MDS storage is cached and loses some but not all writes.

	If the file system is in use and being modified while the ''--mdsdb'' and ''--ostdb'' steps are running, ''lfsck'' may report inconsistencies where none exist due to files and objects being created/removed after the database files were collected. Therefore, the results should be examined closely. You may want to re-run the test ~~and/or [[contact Sun support for guidance]]~~.		If the file system is in use and being modified while the ''--mdsdb'' and ''--ostdb'' steps are running, ''lfsck'' may report inconsistencies where none exist due to files and objects being created/removed after the database files were collected. Therefore, the results should be examined closely. You may want to re-run the test.

	The easiest problem to resolve is that of orphaned objects. When the ''-l'' option for ''lfsck'' is used, these objects are linked to new files and put into lost+found in the Lustre file system, where they can be examined and saved or deleted as necessary. If you are certain the objects are not useful, ''lfsck'' can be run with the ''-d'' option to delete orphaned objects and free up any space they are using.		The easiest problem to resolve is that of orphaned objects. When the ''-l'' option for ''lfsck'' is used, these objects are linked to new files and put into lost+found in the Lustre file system, where they can be examined and saved or deleted as necessary. If you are certain the objects are not useful, ''lfsck'' can be run with the ''-d'' option to delete orphaned objects and free up any space they are using.

Docadmin: /* Running e2fsck+lfsck on a Corrupted Lustre File System */

2009-10-07T17:08:01Z

Running e2fsck+lfsck on a Corrupted Lustre File System

← Older revision		Revision as of 10:08, 7 October 2009
Line 78:		Line 78:
	The easiest problem to resolve is that of orphaned objects. When the ''-l'' option for ''lfsck'' is used, these objects are linked to new files and put into lost+found in the Lustre file system, where they can be examined and saved or deleted as necessary. If you are certain the objects are not useful, ''lfsck'' can be run with the ''-d'' option to delete orphaned objects and free up any space they are using.		The easiest problem to resolve is that of orphaned objects. When the ''-l'' option for ''lfsck'' is used, these objects are linked to new files and put into lost+found in the Lustre file system, where they can be examined and saved or deleted as necessary. If you are certain the objects are not useful, ''lfsck'' can be run with the ''-d'' option to delete orphaned objects and free up any space they are using.

	To fix dangling inodes, ''lfsck'' will create new zero-length objects on the OSTs ~~if the ''-c'' option is used~~. These files will read back with binary zeros for the stripes that had objects recreated. Such files can also be read even without ''lfsck'' repair by using ''dd if=/lustre/bad/file of=/new/file bs=4k conv=sync,noerror''. Because this is rarely useful to have files with large holes in them, most users delete these files after reading them (if useful) and/or restoring them from backup. Note that it is not possible to write to the holes of such a file without having ''lfsck'' recreate the objects, so it is generally easier to delete these files and restore them from backup.		To fix dangling inodes, using ''lfsck'' with the ''-c'' option will create new zero-length objects on the OSTs. These files will read back with binary zeros for the stripes that had objects recreated. Such files can also be read even without ''lfsck'' repair by entering:

	To fix inodes with duplicate objects, ''lfsck'' copies the duplicate object to a new object and assign ~~that~~ to one of the files ~~if the ''-c'' option is given~~. One of the files will be OK, and one will likely contain garbage, but ''lfsck'' cannot tell by itself which one is correct.		<pre>
			dd if=/lustre/bad/file of=/new/file bs=4k conv=sync,noerror
			</pre>

			Because it is rarely useful to have files with large holes in them, most users delete these files after reading them (if useful) and/or restoring them from backup. Note that it is not possible to write to the holes of such a file without having ''lfsck'' recreate the objects, so it is generally easier to delete these files and restore them from backup.

			To fix inodes with duplicate objects, using ''lfsck'' with the ''-c'' option copies the duplicate object to a new object and assign it to one of the files. One of the files will be OK, and one will likely contain garbage, but ''lfsck'' cannot tell by itself which one is correct.

Docadmin: /* Running e2fsck+lfsck on a Corrupted Lustre File System */

2009-10-07T17:04:32Z

Running e2fsck+lfsck on a Corrupted Lustre File System

← Older revision		Revision as of 10:04, 7 October 2009
Line 76:		Line 76:
	If the file system is in use and being modified while the ''--mdsdb'' and ''--ostdb'' steps are running, ''lfsck'' may report inconsistencies where none exist due to files and objects being created/removed after the database files were collected. Therefore, the results should be examined closely. You may want to re-run the test and/or [[contact Sun support for guidance]].		If the file system is in use and being modified while the ''--mdsdb'' and ''--ostdb'' steps are running, ''lfsck'' may report inconsistencies where none exist due to files and objects being created/removed after the database files were collected. Therefore, the results should be examined closely. You may want to re-run the test and/or [[contact Sun support for guidance]].

	The easiest problem to resolve is that of orphaned objects. ~~Using~~ the ''-l'' option to ''lfsck'' ~~it can link~~ these objects to new files and put ~~them~~ into lost+found in the Lustre file system, where they can be examined and saved or deleted as necessary. If you are certain the objects are not useful, ''lfsck'' can be run with the ''-d'' option to delete orphaned objects and free up any space they are using.		The easiest problem to resolve is that of orphaned objects. When the ''-l'' option for ''lfsck'' is used, these objects are linked to new files and put into lost+found in the Lustre file system, where they can be examined and saved or deleted as necessary. If you are certain the objects are not useful, ''lfsck'' can be run with the ''-d'' option to delete orphaned objects and free up any space they are using.

	To fix dangling inodes, ''lfsck'' will create new zero-length objects on the OSTs if the ''-c'' option is used. These files will read back with binary zeros for the stripes that had objects recreated. Such files can also be read even without ''lfsck'' repair by using ''dd if=/lustre/bad/file of=/new/file bs=4k conv=sync,noerror''. Because this is rarely useful to have files with large holes in them, most users delete these files after reading them (if useful) and/or restoring them from backup. Note that it is not possible to write to the holes of such a file without having ''lfsck'' recreate the objects, so it is generally easier to delete these files and restore them from backup.		To fix dangling inodes, ''lfsck'' will create new zero-length objects on the OSTs if the ''-c'' option is used. These files will read back with binary zeros for the stripes that had objects recreated. Such files can also be read even without ''lfsck'' repair by using ''dd if=/lustre/bad/file of=/new/file bs=4k conv=sync,noerror''. Because this is rarely useful to have files with large holes in them, most users delete these files after reading them (if useful) and/or restoring them from backup. Note that it is not possible to write to the holes of such a file without having ''lfsck'' recreate the objects, so it is generally easier to delete these files and restore them from backup.

	To fix inodes with duplicate objects, ''lfsck'' copies the duplicate object to a new object and assign that to one of the files if the ''-c'' option is given. One of the files will be OK, and one will likely contain garbage, but ''lfsck'' cannot tell by itself which one is correct.		To fix inodes with duplicate objects, ''lfsck'' copies the duplicate object to a new object and assign that to one of the files if the ''-c'' option is given. One of the files will be OK, and one will likely contain garbage, but ''lfsck'' cannot tell by itself which one is correct.