From: Christoph Hellwig <hch@infradead.org>
To: CoolCold <coolthecold@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] adding example with xfs_info output decryption
Date: Fri, 22 Jul 2011 11:52:00 -0400 [thread overview]
Message-ID: <20110722155200.GA31867@infradead.org> (raw)
In-Reply-To: <BANLkTikjPhKNBVUamccXbAropDw=oBSRgg@mail.gmail.com>
On Mon, May 23, 2011 at 02:34:54AM +0400, CoolCold wrote:
> Basing on irc discussions and questions about reading xfs_info output
> I've added example in xfs_growfs manpage.
Alex, Dave, Eric, do you guys have any comments on this? Language
nitpicks from the native speakers? Otherwise I'd be inclined to put it
in.
> Signed-off-by: Roman Ovchinnikov <coolthecold@gmail.com>
> ---
> man/man8/xfs_growfs.8 | 34 ++++++++++++++++++++++++++++++++++
> 1 files changed, 34 insertions(+), 0 deletions(-)
>
> diff --git a/man/man8/xfs_growfs.8 b/man/man8/xfs_growfs.8
> index 02793ae..c782fc1 100644
> --- a/man/man8/xfs_growfs.8
> +++ b/man/man8/xfs_growfs.8
> @@ -1,3 +1,14 @@
> +.\" Verbatim blocks taken from openssl req manpage content
> +.de Vb \" Begin verbatim text
> +.ft CW
> +.nf
> +.ne \\$1
> +..
> +.de Ve \" End verbatim text
> +.ft R
> +.fi
> +..
> +
> .TH xfs_growfs 8
> .SH NAME
> xfs_growfs, xfs_info \- expand an XFS filesystem
> @@ -105,6 +116,7 @@ this is specified with
> Specifies that no change to the filesystem is to be made.
> The filesystem geometry is printed, and argument checking is performed,
> but no growth occurs.
> +.B See output examples below.
> .TP
> .BI "\-r | \-R " size
> Specifies that the real-time section of the filesystem should be grown. If the
> @@ -152,6 +164,28 @@ reside. In order to grow a filesystem, it is
> necessary to provide added
> space for it to occupy. Therefore there must be at least one spare new
> disk partition available. Adding the space is often done through the use
> of a logical volume manager.
> +.SH "EXAMPLES"
> +
> +Examining xfs_info output.
> +.PP
> +Let's assume one have the next xfs_info output:
> +.PP
> +.Vb 1
> +\& meta-data=/dev/sda isize=256 agcount=32, agsize=16777184 blks
> +\& = sectsz=512 attr=2
> +\& data = bsize=4096 blocks=536869888, imaxpct=5
> +\& = sunit=32 swidth=128 blks
> +\& naming =version 2 bsize=4096
> +\& log =internal bsize=4096 blocks=32768, version=2
> +\& = sectsz=512 sunit=32 blks, lazy-count=1
> +\& realtime =none extsz=524288 blocks=0, rtextents=0
> +.Ve
> +.PP
> +
> +Here, data section block size (bsize) is 4096 bytes. Therefore
> +"sunit=32 swidth=128 blks" means stripe unit is 32*4096 bytes = 128 kibibytes
> +and stripe width is 128*4096 bytes = 512 kibibytes. Filesystem is striped
> +over 4 ( 128 / 32 ) stripes.
> .SH SEE ALSO
> .BR mkfs.xfs (8),
> .BR md (4),
> --
> 1.7.2.5
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
---end quoted text---
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-22 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 22:34 [PATCH] adding example with xfs_info output decryption CoolCold
2011-07-22 15:52 ` Christoph Hellwig [this message]
2011-07-26 19:02 ` Alex Elder
2011-07-27 9:13 ` Roman Ovchinnikov
2011-07-27 15:28 ` Alex Elder
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=20110722155200.GA31867@infradead.org \
--to=hch@infradead.org \
--cc=coolthecold@gmail.com \
--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