Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] How to use dynamic tracing
Date: Thu, 12 Mar 2009 11:41:23 +0100	[thread overview]
Message-ID: <200903121141.24095.philipp.reisner@linbit.com> (raw)
In-Reply-To: <EAF41105EEA8E14BA54927856CEDEB3D01084707@300813ANEX2.global.avaya.com>

On Wednesday 04 March 2009 20:08:51 Guo, Weiping (Jim) wrote:
> Hi All,
>
> I am new to drbd development. Just want to get my foot wet.
>
> One thing I would to do is turn on the tracing so that I may have a
> quicker way to understand drbd. I defined "ENABLE_DYNAMIC_TRACE" in the
> configuration file, but not sure how to use it.
>
> Any documents or suggestions are appreciated!
>

enum {
	TraceLvlAlways = 0,
	TraceLvlSummary,
	TraceLvlMetrics,
	TraceLvlAll,
	TraceLvlMax
};

enum {
	TraceTypePacket = 0x00000001,
	TraceTypeRq	= 0x00000002,
	TraceTypeUuid	= 0x00000004,
	TraceTypeResync = 0x00000008,
	TraceTypeEE	= 0x00000010,
	TraceTypeUnplug = 0x00000020,
	TraceTypeNl	= 0x00000040,
	TraceTypeALExts = 0x00000080,
	TraceTypeIntRq  = 0x00000100,
	TraceTypeMDIO   = 0x00000200,
	TraceTypeEpochs = 0x00000400,
};

echo 1 > /sys/module/drbd/parameters/trace_devs # Bitmask
echo 3 > /sys/module/drbd/parameters/trace_level
echo 4 > /sys/module/drbd/parameters/trace_type

Enables UUID traceing with full verbosity for /dev/drbd0.


-Phil
-- 
: Dipl-Ing Philipp Reisner
: LINBIT | Your Way to High Availability
: Tel: +43-1-8178292-50, Fax: +43-1-8178292-82
: http://www.linbit.com

DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.



      reply	other threads:[~2009-03-12 10:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 19:08 [Drbd-dev] How to use dynamic tracing Guo, Weiping (Jim)
2009-03-12 10:41 ` Philipp Reisner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200903121141.24095.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=drbd-dev@lists.linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox