From: KELEMEN Peter <Peter.Kelemen@cern.ch>
To: xfs@oss.sgi.com
Subject: [PATCH][DOC] xfs_stats.pl: xs_log_blocks counts in basic blocks
Date: Mon, 28 Jan 2008 11:38:15 +0100 [thread overview]
Message-ID: <20080128103815.GA1777@luba> (raw)
xs_log_blocks is counting in basic blocks, update documentation as
discussed with Eric Sandeen on #xfs.
Index: xfsmisc/xfs_stats.pl
===================================================================
RCS file: /cvs/xfs-cmds/xfsmisc/xfs_stats.pl,v
retrieving revision 1.5
diff -u -u -r1.5 xfs_stats.pl
--- xfsmisc/xfs_stats.pl 10 Feb 2004 17:10:22 -0000 1.5
+++ xfsmisc/xfs_stats.pl 28 Jan 2008 10:34:05 -0000
@@ -337,7 +337,7 @@
=head2 B<xs_log_blocks> (I<xfs.log.blocks>)
-This variable counts the number of Kbytes of information being written
+This variable counts (in 512-byte units) the information being written
to the physical log partitions of all XFS filesystems. Log data traffic
is proportional to the level of meta-data updating. The rate with which
log data gets written depends on the size of internal log buffers and
next reply other threads:[~2008-01-28 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 10:38 KELEMEN Peter [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-26 1:00 [PATCH][DOC] xfs_stats.pl: xs_log_blocks counts in basic blocks KELEMEN Peter
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=20080128103815.GA1777@luba \
--to=peter.kelemen@cern.ch \
--cc=xfs@oss.sgi.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