From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>,
Stan Hoeppner <stan@hardwarefreak.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH 2/2] xfsprogs: don't warn about log sunit size if it was auto-discovered
Date: Wed, 29 Oct 2014 14:38:42 -0400 [thread overview]
Message-ID: <20141029183841.GB4226@bfoster.laptop> (raw)
In-Reply-To: <544FD47D.8020409@sandeen.net>
On Tue, Oct 28, 2014 at 12:38:05PM -0500, Eric Sandeen wrote:
> Today, users doing a bare mkfs on storage with a large default
> stripe size may be surprised to get this warning:
>
> log stripe unit (%d bytes) is too large (maximum is 256KiB
> log stripe unit adjusted to 32KiB
>
> through no fault of their own. The fallback is appropriate
> and harmless, and there's no need to warn about this in the
> defaults case.
>
> However, we keep the warning if a large log stripe unit was
> specified by the user on the commandline.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index a0fed31..66711cb 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -946,6 +946,8 @@ main(
> int logversion;
> int lvflag;
> int lsflag;
> + int lsuflag;
> + int lsunitflag;
> int lsectorlog;
> int lsectorsize;
> int lslflag;
> @@ -1004,7 +1006,7 @@ main(
> sectorsize = lsectorsize = XFS_MIN_SECTORSIZE;
> agsize = daflag = dasize = dblocks = 0;
> ilflag = imflag = ipflag = isflag = 0;
> - liflag = laflag = lsflag = ldflag = lvflag = 0;
> + liflag = laflag = lsflag = lsuflag = lsunitflag = ldflag = lvflag = 0;
> loginternal = 1;
> logversion = 2;
> logagno = logblocks = rtblocks = rtextblocks = 0;
> @@ -1400,6 +1402,7 @@ main(
> respec('l', lopts, L_SU);
> lsu = cvtnum(
> blocksize, sectorsize, value);
> + lsuflag = 1;
> break;
> case L_SUNIT:
> if (!value || *value == '\0')
> @@ -1412,6 +1415,7 @@ main(
> usage();
> }
> lsunit = cvtnum(0, 0, value);
> + lsunitflag = 1;
> break;
> case L_NAME:
> case L_DEV:
> @@ -2379,11 +2383,15 @@ an AG size that is one stripe unit smaller, for example %llu.\n"),
> }
>
> if (logversion == 2 && (lsunit * blocksize) > 256 * 1024) {
> - fprintf(stderr,
> + /* Warn only if specified on commandline */
> + if (lsuflag || lsunitflag) {
> + fprintf(stderr,
> _("log stripe unit (%d bytes) is too large (maximum is 256KiB)\n"),
> - (lsunit * blocksize));
> + (lsunit * blocksize));
> + fprintf(stderr,
> + _("log stripe unit adjusted to 32KiB\n"));
> + }
Right above this particular hunk we have the possibility of lsunit
inheriting a value from dsunit. If the latter is specified by the user,
we don't print the message for an arguably user-specified lsunit. Hmm,
do we care about that case?
Brian
> lsunit = (32 * 1024) >> blocklog;
> - fprintf(stderr, _("log stripe unit adjusted to 32KiB\n"));
> }
>
> min_logblocks = max_trans_res(crcs_enabled, dirversion,
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2014-10-29 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:35 [PATCH 1/2] xfsprogs: ignore stripe geom if sunit or swidth == physical sector size Eric Sandeen
2014-10-28 17:38 ` [PATCH 2/2] xfsprogs: don't warn about log sunit size if it was auto-discovered Eric Sandeen
2014-10-29 18:38 ` Brian Foster [this message]
2014-10-29 18:45 ` Eric Sandeen
2014-10-29 19:57 ` Brian Foster
2014-10-29 18:37 ` [PATCH 1/2] xfsprogs: ignore stripe geom if sunit or swidth == physical sector size Brian Foster
2014-10-29 18:47 ` Eric Sandeen
2014-10-29 21:38 ` Stan Hoeppner
2014-10-30 11:46 ` Brian Foster
2014-10-30 19:15 ` Stan Hoeppner
2014-10-30 19:50 ` Brian Foster
2014-10-30 20:15 ` Stan Hoeppner
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=20141029183841.GB4226@bfoster.laptop \
--to=bfoster@redhat.com \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
--cc=stan@hardwarefreak.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