linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
	linux-xfs@vger.kernel.org, snitzer@redhat.com, hare@suse.de,
	axboe@kernel.dk, mwilck@suse.com,
	Damien Le Moal <damien.lemoal@wdc.com>,
	Bart Van Assche <Bart.VanAssche@wdc.com>
Subject: Re: [PATCH] libxfs: detect zoned disks and prevent their raw use
Date: Fri, 15 Jun 2018 23:52:00 +0200	[thread overview]
Message-ID: <20180615215200.GR5527@wotan.suse.de> (raw)
In-Reply-To: <5fbcde14-fdb8-9a4f-e578-4ad7c4ef6315@sandeen.net>

On Fri, Jun 15, 2018 at 04:48:29PM -0500, Eric Sandeen wrote:
> 
> 
> On 6/15/18 3:50 PM, Luis R. Rodriguez wrote:
> > +	if (ret == 1) {
> > +		fprintf(stderr,
> > +_("%s: zoned disk detected, refer to dm-zoned-tools for how to use with XFS\n"),
> > +			path);
> > +		exit(1);
> 
> Sorry for not sending this before V2, but is "dm-zoned-tools" established enough
> in the ecosystem at this point to embed it in help text of utilities like this?
> 
> (It's not in debian or in fedora, so that message might lead to some head-scratching,
> I think)

It *should*, I'll help up clean that project up a bit now with some meta crap which
Debian police may want, but yeah not sure. You're call. Whatever you wish to
print I'm fine with.

AFAICT dmzadm *should* be packaged at least. Long term perhaps lvm2 may re-implement
it, but I can't see why folks should wait for such lofty vaporware.

  Luis

  reply	other threads:[~2018-06-15 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 20:50 [PATCH] libxfs: detect zoned disks and prevent their raw use Luis R. Rodriguez
2018-06-15 20:56 ` Bart Van Assche
2018-06-15 20:59 ` Darrick J. Wong
2018-06-15 21:48 ` Eric Sandeen
2018-06-15 21:52   ` Luis R. Rodriguez [this message]
2018-06-16  0:13 ` Dave Chinner

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=20180615215200.GR5527@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=Bart.VanAssche@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@wdc.com \
    --cc=hare@suse.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mwilck@suse.com \
    --cc=sandeen@sandeen.net \
    --cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).