From: Carlos Maiolino <cmaiolino@redhat.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>,
Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH] mkfs: avoid divide-by-zero when hardware reports optimal i/o size as 0
Date: Fri, 20 Jul 2018 17:55:29 +0200 [thread overview]
Message-ID: <20180720155529.qw7nthesfu6xu7ie@odin.usersys.redhat.com> (raw)
In-Reply-To: <6f62dbc6-f516-e8b5-1f08-6be227a61219@suse.com>
On Thu, Jul 19, 2018 at 05:23:22PM -0400, Jeff Mahoney wrote:
> Commit 051b4e37f5e (mkfs: factor AG alignment) factored out the
> AG alignment code into a separate function. It got rid of
> redundant checks for dswidth != 0 since calc_stripe_factors was
> supposed to guarantee that if dsunit is non-zero dswidth will be
> as well. Unfortunately, there's hardware out there that reports its
> optimal i/o size as larger than the maximum i/o size, which the kernel
> treats as broken and zeros out the optimal i/o size. We'll accept
> the multi-sector dsunit but have a zero dswidth and hit a divide-by-zero
> in align_ag_geometry.
>
> To resolve this we can check the topology before consuming it, default
> to using the stripe unit as the stripe width, and warn the user about it.
>
I wonder if this shouldn't go into blkid_get_topology since something is wrong
with the information reported by the storage.
And require a force_overwrite to continue, at this point, something looks quite
wrong in the storage, and I think this is the last 'resource' a sysadmin will
have to notice this before making the FS, and start using it, so, maybe requiring
force_overwrite would bring more attention.
> Fixes: 051b4e37f5e (mkfs: factor AG alignment)
> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
> ---
> mkfs/xfs_mkfs.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index a135e06e..35542e57 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -2295,6 +2295,12 @@ _("data stripe width (%d) must be a multiple of the data stripe unit (%d)\n"),
> if (!dsunit) {
> dsunit = ft->dsunit;
> dswidth = ft->dswidth;
> + if (dsunit && dswidth == 0) {
> + fprintf(stderr,
> +_("%s: Volume reports stripe unit of %d bytes but stripe width of 0. Using stripe width of %d bytes, which may not be optimal.\n"),
> + progname, dsunit << 9, dsunit << 9);
> + dswidth = dsunit;
> + }
> use_dev = true;
> } else {
> /* check and warn is alignment is sub-optimal */
> --
> 2.16.4
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Carlos
next prev parent reply other threads:[~2018-07-20 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 21:23 [PATCH] mkfs: avoid divide-by-zero when hardware reports optimal i/o size as 0 Jeff Mahoney
2018-07-20 15:55 ` Carlos Maiolino [this message]
2018-07-20 16:19 ` Darrick J. Wong
2018-07-23 12:21 ` Carlos Maiolino
2018-07-20 18:08 ` Jeff Mahoney
2018-07-31 2:10 ` Eric Sandeen
2018-07-31 2:14 ` Eric Sandeen
2018-07-31 2:57 ` [PATCH 2/1] mkfs: factor stripe geom validator & use for cli + device Eric Sandeen
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=20180720155529.qw7nthesfu6xu7ie@odin.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=david@fromorbit.com \
--cc=jeffm@suse.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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;
as well as URLs for NNTP newsgroup(s).