ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Marcos E. Matsunaga <Marcos.Matsunaga@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] how to use run_lvb_torture.py ?
Date: Mon Mar 17 05:09:24 2008	[thread overview]
Message-ID: <47DE5F27.3000508@oracle.com> (raw)
In-Reply-To: <47DDF1CD.50901@suse.de>

Coly,

You don't have to specify the hbdev. You will have the partition mounted 
to run this test.

Make sure you set /dlm directory to 777. The user needs to have full 
access to /dlm.

The domain is the UUID of the volume you are using.

debugfs.ocfs2 -R stats <device> |grep UUID

As for the lockname, I usually choose the biggest file I have on the 
partition.

To get the lockname:


debugfs.ocfs2 -R "encode <filepath>" <device>



Regards,

Marcos Eduardo Matsunaga

Oracle USA
Linux Engineering

?The statements and opinions expressed here are my own and do not
necessarily represent those of Oracle Corporation.?



Coly Li wrote:
> When I tried to run run_lvb_torture.py, there were some parameters I don't know how to use.
>
> >From the usage information,
> run_lvb_torture.py [-d | --dlmfs <dlmfs path>] [-i | --iteractions <iteractions>] [-H | --hbdev
> <heartbeat device>] [-l | --logfile <logfile>] [-n | --nodelist <nodelist>] <domain> <lockname>
> [-h|--help]
>
> 1) what is heartbeat device? Should I create a separated ocfs2 partition as a heartbeat device ?
> 2) what is domain and lockname ? how to set it ?
>
> I tried to google it and check the code, since I do not have clear conception for domain/lockname,
> the information was very limited for me.
>
> Thanks in advance.
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20080317/2472680d/attachment.html

  reply	other threads:[~2008-03-17  5:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 16:32 [Ocfs2-devel] Backports to OCFS2 1.4 Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 08/18] ocfs2: Correct use of ! and & in aops.c Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 07/18] ocfs2: make dlm_do_assert_master() static Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 01/18] ocfs2: Add helper task_pid_nr Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 05/18] ocfs2: possible cleanups Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 04/18] ocfs2: Fix writeout in ocfs2_data_convert_worker() Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 06/18] ocfs2: make ocfs2_downconvert_thread() static Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 02/18] ocfs2: Spelling fixes Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 11/18] ocfs2: Fix endian bug in o2dlm protocol negotiation Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 14/18] ocfs2/dlm: Add missing dlm_lockres_put()s in migration path Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 16/18] ocfs2/dlm: Print message showing the recovery master Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 15/18] ocfs2/dlm: Add missing dlm_lockres_put()s Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 03/18] ocfs2: Negotiate locking protocol versions Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 12/18] ocfs2: Fix an endian bug in online resize Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 10/18] ocfs2: Use dlm_print_one_lock_resource for lock resource print Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 09/18] ocfs2/dlm: fix printk warning Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 17/18] ocfs2/dlm: dlm_thread should not sleep while holding the dlm_spinlock Sunil Mushran
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 18/18] ocfs2: Fix NULL pointer dereferences in o2net Sunil Mushran
2008-03-16 21:10   ` [Ocfs2-devel] how to use run_lvb_torture.py ? Coly Li
2008-03-17  5:09     ` Marcos E. Matsunaga [this message]
2008-03-11 16:32 ` [Ocfs2-devel] [PATCH 13/18] ocfs2/dlm: Add missing dlm_lock_put()s Sunil Mushran

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=47DE5F27.3000508@oracle.com \
    --to=marcos.matsunaga@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).