Lustre Debugging for Developers - Revision history

Sbarthel: /* Finding memory leaks using leak_finder.pl */

2011-01-20T15:18:11Z

Finding memory leaks using leak_finder.pl

← Older revision		Revision as of 08:18, 20 January 2011
Line 21:		Line 21:
	Memory leaks can occur in code when memory has been allocated and then not freed once it is no longer required. The ''leak_finder.pl'' program provides a way to find memory leaks.		Memory leaks can occur in code when memory has been allocated and then not freed once it is no longer required. The ''leak_finder.pl'' program provides a way to find memory leaks.

	For details, see [http://wiki.lustre.org/manual/~~LustreManual18_HTML~~/LustreDebugging.html#~~50651266_pgfId~~-~~1291477~~ Section 24.2.4: ''Finding Memory Leaks''] in the [http://wiki.lustre.org/manual/LustreManual20_HTML/index.html ''Lustre Operations Manual''].		For details, see [http://wiki.lustre.org/manual/LustreManual20_HTML/LustreDebugging.html#50438274_pgfId-1296154 Section 28.3.3: ''Finding Memory Leaks Using leak_finder.pl''] in the [http://wiki.lustre.org/manual/LustreManual20_HTML/index.html ''Lustre Operations Manual''].

	=Using LWT Tracing=		=Using LWT Tracing=

Sbarthel: /* Accessing a ptlrpc Request History */

2011-01-20T15:17:17Z

Accessing a ptlrpc Request History

← Older revision		Revision as of 08:17, 20 January 2011
Line 15:		Line 15:
	Each service maintains a request history, which can be useful for first occurrence troubleshooting. ''Prlrpc'' is an RPC protocol layered on LNET. This protocol deals with stateful servers and has semantics and built in support for recovery. ''Prlrpc'' is a subsystem in the Lustre Debug Messages section.		Each service maintains a request history, which can be useful for first occurrence troubleshooting. ''Prlrpc'' is an RPC protocol layered on LNET. This protocol deals with stateful servers and has semantics and built in support for recovery. ''Prlrpc'' is a subsystem in the Lustre Debug Messages section.

	For more information about how to use ''prlrpc'', see [http://wiki.lustre.org/manual/~~LustreManual18_HTML~~/LustreDebugging.html#~~50651266_pgfId~~-~~1291584~~ Section 24.5: ''Ptlrpc Request History''] in the [http://wiki.lustre.org/manual/LustreManual20_HTML/index.html ''Lustre Operations Manual''].		For more information about how to use ''prlrpc'', see [http://wiki.lustre.org/manual/LustreManual20_HTML/LustreDebugging.html#50438274_pgfId-1296100 Section 28.3.2: ''Accessing a Ptlrpc Request History''] in the [http://wiki.lustre.org/manual/LustreManual20_HTML/index.html ''Lustre Operations Manual''].

	=Finding memory leaks using ''leak_finder.pl''=		=Finding memory leaks using ''leak_finder.pl''=

Sbarthel: /* Adding Debugging to the Source Code */

2011-01-20T15:16:07Z

Adding Debugging to the Source Code

← Older revision		Revision as of 08:16, 20 January 2011
Line 10:		Line 10:
	#define DEBUG_SUBSYSTEM S_PORTALS		#define DEBUG_SUBSYSTEM S_PORTALS

	A list of available macros with descriptions is provided in see [http://wiki.lustre.org/manual/~~LustreManual18_HTML~~/LustreDebugging.html#~~50651266_pgfId~~-~~1291518~~ Section 24.2.8: ''Adding Debugging to the Lustre Source Code''] in the [http://wiki.lustre.org/manual/LustreManual20_HTML/index.html ''Lustre Operations Manual''].		A list of available macros with descriptions is provided in see [http://wiki.lustre.org/manual/LustreManual20_HTML/LustreDebugging.html#50438274_pgfId-1296027 Section 28.3.1: ''Adding Debugging to the Lustre Source Code''] in the [http://wiki.lustre.org/manual/LustreManual20_HTML/index.html ''Lustre Operations Manual''].

	== Accessing a ''ptlrpc'' Request History ==		== Accessing a ''ptlrpc'' Request History ==

Sbarthel at 15:15, 20 January 2011

2011-01-20T15:15:10Z

← Older revision		Revision as of 08:15, 20 January 2011
Line 10:		Line 10:
	#define DEBUG_SUBSYSTEM S_PORTALS		#define DEBUG_SUBSYSTEM S_PORTALS

	A list of available macros with descriptions is provided in see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291518 Section 24.2.8: ''Adding Debugging to the Lustre Source Code''] in the [~~[Lustre Documentation\|~~''Lustre Operations Manual'']].		A list of available macros with descriptions is provided in see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291518 Section 24.2.8: ''Adding Debugging to the Lustre Source Code''] in the [http://wiki.lustre.org/manual/LustreManual20_HTML/index.html ''Lustre Operations Manual''].

	== Accessing a ''ptlrpc'' Request History ==		== Accessing a ''ptlrpc'' Request History ==
	Each service maintains a request history, which can be useful for first occurrence troubleshooting. ''Prlrpc'' is an RPC protocol layered on LNET. This protocol deals with stateful servers and has semantics and built in support for recovery. ''Prlrpc'' is a subsystem in the Lustre Debug Messages section.		Each service maintains a request history, which can be useful for first occurrence troubleshooting. ''Prlrpc'' is an RPC protocol layered on LNET. This protocol deals with stateful servers and has semantics and built in support for recovery. ''Prlrpc'' is a subsystem in the Lustre Debug Messages section.

	For more information about how to use ''prlrpc'', see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291584 Section 24.5: ''Ptlrpc Request History''] in the [~~[Lustre Documentation\|~~''Lustre Operations Manual'']].		For more information about how to use ''prlrpc'', see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291584 Section 24.5: ''Ptlrpc Request History''] in the [http://wiki.lustre.org/manual/LustreManual20_HTML/index.html ''Lustre Operations Manual''].

	=Finding memory leaks using ''leak_finder.pl''=		=Finding memory leaks using ''leak_finder.pl''=
Line 21:		Line 21:
	Memory leaks can occur in code when memory has been allocated and then not freed once it is no longer required. The ''leak_finder.pl'' program provides a way to find memory leaks.		Memory leaks can occur in code when memory has been allocated and then not freed once it is no longer required. The ''leak_finder.pl'' program provides a way to find memory leaks.

	For details, see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291477 Section 24.2.4: ''Finding Memory Leaks''] in the [~~[Lustre Documentation\|~~''Lustre Operations Manual'']].		For details, see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291477 Section 24.2.4: ''Finding Memory Leaks''] in the [http://wiki.lustre.org/manual/LustreManual20_HTML/index.html ''Lustre Operations Manual''].

	=Using LWT Tracing=		=Using LWT Tracing=

Docadmin: /* Using LWT Tracing */

2011-01-07T21:03:51Z

Using LWT Tracing

← Older revision		Revision as of 14:03, 7 January 2011
Line 24:		Line 24:

	=Using LWT Tracing=		=Using LWT Tracing=
	Lustre offers a lightweight tracing facility called LWT. It prints fixed size requests into a buffer and is much faster than LDEBUG. The LWT tracking facility can be used to debug difficult problems. Use of LWT tracing requires rebuilding ~~Lustre~~ code.		Lustre offers a lightweight tracing facility called LWT. It prints fixed size requests into a buffer and is much faster than LDEBUG. The LWT tracking facility can be used to debug difficult problems. Use of LWT tracing requires rebuilding LNET code.

	Dumped LWT trace-based records contain:		Dumped LWT trace-based records contain:

Docadmin at 21:02, 7 January 2011

2011-01-07T21:02:54Z

@@ Line 1: / Line 1: @@
-<small>''(Updated: Feb 2010)''</small>
+<small>''(Updated: Jan 2011)''</small>
 __TOC__
 The procedures below may be useful to developers debugging Lustre code.
@@ Line 22: / Line 22: @@
 For details, see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291477 Section 24.2.4: ''Finding Memory Leaks''] in the [[Lustre Documentation|''Lustre Operations Manual'']].

Sbarthel: /* Finding memory leaks using leak_finder.pl */

2010-12-07T19:44:23Z

Finding memory leaks using leak_finder.pl

← Older revision		Revision as of 12:44, 7 December 2010
Line 21:		Line 21:
	Memory leaks can occur in code when memory has been allocated and then not freed once it is no longer required. The ''leak_finder.pl'' program provides a way to find memory leaks.		Memory leaks can occur in code when memory has been allocated and then not freed once it is no longer required. The ''leak_finder.pl'' program provides a way to find memory leaks.

	For details, see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#~~50598018_pgfId~~-1291477 Section 23.2.4: ''Finding Memory Leaks''] in the [[Lustre Documentation\|''Lustre Operations Manual'']].		For details, see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291477 Section 24.2.4: ''Finding Memory Leaks''] in the [[Lustre Documentation\|''Lustre Operations Manual'']].

Sbarthel: /* Accessing a ptlrpc Request History */

2010-12-07T19:43:30Z

Accessing a ptlrpc Request History

← Older revision		Revision as of 12:43, 7 December 2010
Line 15:		Line 15:
	Each service maintains a request history, which can be useful for first occurrence troubleshooting. ''Prlrpc'' is an RPC protocol layered on LNET. This protocol deals with stateful servers and has semantics and built in support for recovery. ''Prlrpc'' is a subsystem in the Lustre Debug Messages section.		Each service maintains a request history, which can be useful for first occurrence troubleshooting. ''Prlrpc'' is an RPC protocol layered on LNET. This protocol deals with stateful servers and has semantics and built in support for recovery. ''Prlrpc'' is a subsystem in the Lustre Debug Messages section.

	For more information about how to use ''prlrpc'', see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#~~50598018_47732~~ Section 23.5: ''Ptlrpc Request History''] in the [[Lustre Documentation\|''Lustre Operations Manual'']].		For more information about how to use ''prlrpc'', see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291584 Section 24.5: ''Ptlrpc Request History''] in the [[Lustre Documentation\|''Lustre Operations Manual'']].

	=Finding memory leaks using ''leak_finder.pl''=		=Finding memory leaks using ''leak_finder.pl''=

Sbarthel: /* Adding Debugging to the Source Code */

2010-12-07T19:40:12Z

Adding Debugging to the Source Code

← Older revision		Revision as of 12:40, 7 December 2010
Line 10:		Line 10:
	#define DEBUG_SUBSYSTEM S_PORTALS		#define DEBUG_SUBSYSTEM S_PORTALS

	A list of available macros with descriptions is provided in see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#~~50598018_pgfId~~-1291518 Section 23.2.8: ''Adding Debugging to the Lustre Source Code''] in the [[Lustre Documentation\|''Lustre Operations Manual'']].		A list of available macros with descriptions is provided in see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50651266_pgfId-1291518 Section 24.2.8: ''Adding Debugging to the Lustre Source Code''] in the [[Lustre Documentation\|''Lustre Operations Manual'']].

	== Accessing a ''ptlrpc'' Request History ==		== Accessing a ''ptlrpc'' Request History ==

Docadmin: /* Finding memory leaks using leak_finder.pl */

2010-03-27T21:13:43Z

Finding memory leaks using leak_finder.pl

← Older revision		Revision as of 14:13, 27 March 2010
Line 21:		Line 21:
	Memory leaks can occur in code when memory has been allocated and then not freed once it is no longer required. The ''leak_finder.pl'' program provides a way to find memory leaks.		Memory leaks can occur in code when memory has been allocated and then not freed once it is no longer required. The ''leak_finder.pl'' program provides a way to find memory leaks.

	For details, see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#~~50638978_pgfId~~-1291477 Section 23.2.4: ''Finding Memory Leaks''] in the [[Lustre Documentation\|''Lustre Operations Manual'']].		For details, see [http://wiki.lustre.org/manual/LustreManual18_HTML/LustreDebugging.html#50598018_pgfId-1291477 Section 23.2.4: ''Finding Memory Leaks''] in the [[Lustre Documentation\|''Lustre Operations Manual'']].