[Linux-cluster] GFS Journaling: How to interpret gfs_tool jindex output?

[Sridharan Ramaswamy (srramasw)]

I'm trying to measure the usage of journal blocks created within a GFS
disk. I'm running bonnie++ small file test hoping to overwhelm the
journal with lot of entries to measure its peak usage. I saw gfs_tool
prints jindex data structure. Can anyone help to interpret its output?
 
Also I like to hear from anyone who went through similar exercise of
understanding GFS journal usage in an active system.
 
thanks,
Sridharan
 
[root at cfs1 cluster]$ gfs_tool jindex /mnt/gfs2
  mh_magic = 0x01161970
  mh_type = 4
  mh_generation = 0
  mh_format = 400
  mh_incarn = 0
  no_formal_ino = 21
  no_addr = 21
  di_mode = 0600
  di_uid = 0
  di_gid = 0
  di_nlink = 1
  di_size = 240
  di_blocks = 1
  di_atime = 1171308008
  di_mtime = 1171308008
  di_ctime = 1171308008
  di_major = 0
  di_minor = 0
  di_rgrp = 0
  di_goal_rgrp = 0
  di_goal_dblk = 0
  di_goal_mblk = 0
  di_flags = 0x00000001
  di_payload_format = 1000
  di_type = 1
  di_height = 0
  di_incarn = 0
  di_pad = 0
  di_depth = 0
  di_entries = 0
  no_formal_ino = 0
  no_addr = 0
  di_eattr = 0
  di_reserved =
...
 
Journal 0:
 
  ji_addr = 61728
  ji_nsegment = 63
  ji_pad = 0
  ji_reserved =
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20070212/5596c542/attachment.htm>