public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: dwysocha@redhat.com, xfs@oss.sgi.com
Subject: Re: [PATCH] mkfs.xfs.8: Clarify mkfs vs. mount block size limits.
Date: Sat, 23 Jan 2016 08:13:26 -0500	[thread overview]
Message-ID: <20160123131326.GB2795@bfoster.bfoster> (raw)
In-Reply-To: <56A02144.9030206@redhat.com>

On Wed, Jan 20, 2016 at 06:07:32PM -0600, Eric Sandeen wrote:
> The current explanation is a bit vague to the uninitiated;
> clarify the text to make it obvious that while the mkfs.xfs
> utility is able to create valid filesystems with block sizes
> up to 65536, the Linux kernel can only mount filesystems with
> page sized or smaller blocks.
> 
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---

Reviewed-by: Brian Foster <bfoster@redhat.com>

> 
> diff --git a/man/man8/mkfs.xfs.8 b/man/man8/mkfs.xfs.8
> index 1fe510b..980c7bc 100644
> --- a/man/man8/mkfs.xfs.8
> +++ b/man/man8/mkfs.xfs.8
> @@ -126,7 +126,10 @@ or in bytes with
>  .BR size= .
>  The default value is 4096 bytes (4 KiB), the minimum is 512, and the
>  maximum is 65536 (64 KiB).
> -XFS on Linux currently only supports pagesize or smaller blocks.
> +Although
> +.B mkfs.xfs
> +will accept any of these values and create a valid filesystem,
> +XFS on Linux can only mount filesystems with pagesize or smaller blocks.
>  .TP
>  .BI \-m " global_metadata_options"
>  These options specify metadata format options that either apply to the entire
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2016-01-23 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  0:07 [PATCH] mkfs.xfs.8: Clarify mkfs vs. mount block size limits Eric Sandeen
2016-01-23 13:13 ` Brian Foster [this message]

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=20160123131326.GB2795@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=dwysocha@redhat.com \
    --cc=sandeen@redhat.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