All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: aalbersh@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs_db: improve the fsmap man page entry
Date: Mon, 31 Aug 2026 07:46:04 -0700	[thread overview]
Message-ID: <20260831144604.GE6072@frogsfrogsfrogs> (raw)
In-Reply-To: <20260831071152.2580927-1-hch@lst.de>

On Mon, Aug 31, 2026 at 10:11:52AM +0300, Christoph Hellwig wrote:
> Improve documentation of the flags and optional arguments, and fix up
> messed up formatting.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

I wonder if it's worth documenting that fsmap -l shows external
log device mappings?

Looks better in any case so
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
>  man/man8/xfs_db.8 | 16 +++++++++++++---
>  1 file changed, 13 insertions(+), 3 deletions(-)
> 
> diff --git a/man/man8/xfs_db.8 b/man/man8/xfs_db.8
> index ba2a68211ef2..89db535d38c9 100644
> --- a/man/man8/xfs_db.8
> +++ b/man/man8/xfs_db.8
> @@ -849,14 +849,24 @@ command to convert to and from this form. Block numbers given for file blocks
>  .B bmap
>  command) are in this form.
>  .TP
> -.BI "fsmap [ " start " ] [ " end " ]
> +.BI "fsmap [\-r] [" start " [" end ]]
>  Prints the mapping of disk blocks used by an XFS filesystem.  The map
>  lists each extent used by files, allocation group metadata,
>  journalling logs, and static filesystem metadata, as well as any
>  regions that are unused.  All blocks, offsets, and lengths are specified
>  in units of 512-byte blocks, no matter what the filesystem's block size is.
> -.BI "The optional " start " and " end " arguments can be used to constrain
> -the output to a particular range of disk blocks.
> +.IP
> +The optional
> +.I start
> +and
> +.I end
> +arguments can be used to constrain the output to a particular range of disk
> +blocks.
> +.IP
> +When the
> +.B \-r
> +option is specified, prints the reverse mapping for the real-time device
> +instead of the data device.
>  .TP
>  .BI "fuzz [\-c] [\-d] " "field action"
>  Write garbage into a specific structure field on disk.
> -- 
> 2.53.0
> 
> 

  reply	other threads:[~2026-08-31 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  7:11 [PATCH] xfs_db: improve the fsmap man page entry Christoph Hellwig
2026-08-31 14:46 ` Darrick J. Wong [this message]
2026-09-01  8:08   ` Christoph Hellwig
2026-09-01 14:06     ` Darrick J. Wong

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=20260831144604.GE6072@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.