Handling Full OSTs - Revision history

Sbarthel at 15:38, 22 February 2010

2010-02-22T15:38:47Z

← Older revision		Revision as of 08:38, 22 February 2010
Line 1:		Line 1:
			<small>''(Updated: Oct 2009)''</small>
	__TOC__		__TOC__
	Sometimes a Lustre™ file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs. The procedures below describe how to handle a full OST.		Sometimes a Lustre™ file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs. The procedures below describe how to handle a full OST.
Line 150:		Line 151:
	10 UP osc lustre-OST0005-osc lustre-mdtlov_UUID		10 UP osc lustre-OST0005-osc lustre-mdtlov_UUID
	</pre>		</pre>

	~~''(Updated 10/09)''~~

2010-02-18T18:31:18Z

← Older revision		Revision as of 11:31, 18 February 2010
Line 150:		Line 150:
	10 UP osc lustre-OST0005-osc lustre-mdtlov_UUID		10 UP osc lustre-OST0005-osc lustre-mdtlov_UUID
	</pre>		</pre>

			''(Updated 10/09)''

2009-12-16T18:02:06Z

Protected "Handling Full OSTs" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 11:02, 16 December 2009
(No difference)

2009-12-16T18:01:57Z

← Older revision		Revision as of 11:01, 16 December 2009
Line 1:		Line 1:
	__TOC__		__TOC__
	Sometimes ~~the~~ file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs. The procedures below describe how to handle a full OST.		Sometimes a Lustre™ file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs. The procedures below describe how to handle a full OST.

	== Checking File System Usage ==		== Checking File System Usage ==

2009-10-19T16:52:06Z

← Older revision		Revision as of 09:52, 19 October 2009
Line 1:		Line 1:
	__TOC__		__TOC__
	Sometimes the file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs. The procedures below describe how to handle a full OST.		Sometimes the file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs. The procedures below describe how to handle a full OST.


	== Checking File System Usage ==		== Checking File System Usage ==

2009-10-19T16:51:55Z

← Older revision		Revision as of 09:51, 19 October 2009
Line 1:		Line 1:
	__TOC__		__TOC__
	Sometimes the file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs.		Sometimes the file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs. The procedures below describe how to handle a full OST.

2009-10-19T16:50:41Z

← Older revision		Revision as of 09:50, 19 October 2009
Line 1:		Line 1:
			__TOC__
	Sometimes the file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs.		Sometimes the file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs.


	== Checking File System Usage ==		== Checking File System Usage ==

2009-10-19T16:46:16Z

@@ Line 1: / Line 1: @@
 Sometimes the file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs.
 The example below shows an unbalanced file system:
@@ Line 27: / Line 28: @@
 1017192448 bytes (1.0 GB) copied, 23.2411 seconds, 43.8 MB/s
 </pre>
 To enable continued use of the file system, the full OST has to be taken offline or, more specifically, rendered read-only using the ''lctl'' command. This is done on the MDS, since the MSD allocates space for writing.
@@ Line 77: / Line 80: @@
 The device list shows that ''OST2'' is now inactive. If a new file is now written to the file system, the write will be successful as the stripes are allocated across the remaining active OSTs.

2009-10-03T00:36:17Z

← Older revision		Revision as of 17:36, 2 October 2009
Line 1:		Line 1:
	~~[[Should this be a subtopic under an umbrella topic called "Managing the File System".]]~~

	~~[[Subtopics in Torben's paper include:]]~~

	~~[[* Using Stripes]]~~

	~~[[* Handling Full OSTs]]~~

	~~[[* Migrating Data within a File System]]~~

	~~[[(Do we need to change these headings to reuse this content?)]]~~

	~~----~~

	Sometimes the file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs.		Sometimes the file system becomes unbalanced, often due to changed stripe settings. If an OST is full and an attempt is made to write more information to the file system, an error occurs.

2009-09-25T21:33:01Z

← Older revision		Revision as of 14:33, 25 September 2009
Line 9:		Line 9:
	[[* Migrating Data within a File System]]		[[* Migrating Data within a File System]]

	[[(Do we need to change these ~~heading~~ to reuse this content?)]]		[[(Do we need to change these headings to reuse this content?)]]

	----		----