From: Jan Tulak <jtulak@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH v3] xfsprogs: blkid is now mandatory
Date: Tue, 4 Aug 2015 11:30:30 -0400 (EDT) [thread overview]
Message-ID: <1050814645.2742881.1438702230663.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <55BFA2C5.20408@redhat.com>
----- Original Message -----
> From: "Eric Sandeen" <sandeen@redhat.com>
> To: "Jan Tulak" <jtulak@redhat.com>, "Christoph Hellwig" <hch@infradead.org>
> Cc: xfs@oss.sgi.com
> Sent: Monday, August 3, 2015 7:20:05 PM
> Subject: Re: [PATCH v3] xfsprogs: blkid is now mandatory
>
> On 8/3/15 3:40 AM, Jan Tulak wrote:
> >
> >
> > ----- Original Message -----
> >> From: "Christoph Hellwig" <hch@infradead.org>
> >>
> >> On Tue, Jul 21, 2015 at 08:39:36AM -0400, Jan Tulak wrote:
> >>> I just found that while it is possible to get blkid on OS X, it is
> >>> in 1.0.0 version which doesn't have blkid_probe_get function.
> >>> I'm examining whether it is possible to get an updated version there,
> >>> but right now, this patch breaks OS X support. Unfortunately I didn't
> >>> noticed of this before, as the OS X port was terribly out of date.
> >>>
> >>> So this patch shouldn't be included until I find how to get around.
> >>
> >> I don't think this is a lbocker given that OSX support doesn't
> >> even work.
> >>
> >> To the contrary I'd really prefer to go in ASAP to avoid anyone
> >> relying on it longer than nessecary.
> >
> > I tried to get newer blkid on OSX, but so far without a big success
> > (well, it looks like a kind of a small dependency hell that would
> > have to be ported, with bigger or smaller effort...). With regards
> > on the priorities, I think if we can make the OS X support in
> > "manual patching required" way, then?
> >
> > So lets include this patch, and just note it OS X doc "you have to revert
> > commit XXX and re-apply any changes to the relevant code"?
>
> IIRC block device signature detection isn't really required, it's just
> a nice-to-have; perhaps if blkid isn't present, that functionality can
> simply be disabled?
Signature detection (if I understand you correctly 'signature of existing
FS') could be really disabled, I think. That would take care of
check_overwrite(). However, blkid is also used in get_topology. That one
calls blkid_get_topology, which uses blkid's functions for finding out
sector and io sizes.
What I really can do is to say "on osx, you can mkfs only files," and cut
out the blkid parts. But it limits the usage on OS X even further.
Although, the removed code for non-blkid systems used platform_findsizes
as fallback. Are there some ugly, terrible monsters who would jump from
under the bed when doing that?
However, this patch affects only mkfs. It still should be possible to use
xfs_db and xfs_repair even on block devices.
Cheers,
Jan
--
Jan Tulak
jtulak@redhat.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-04 15:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 16:01 [PATCH] xfsprogs: blkid is now mandatory Jan Tulak
2015-07-01 22:55 ` Dave Chinner
2015-07-02 10:27 ` Jan Tulak
2015-07-02 10:43 ` [PATCH v2] " Jan Tulak
2015-07-03 15:19 ` Christoph Hellwig
2015-07-03 23:45 ` Dave Chinner
2015-07-07 15:10 ` Jan Tulak
2015-07-08 9:14 ` [PATCH v3] " Jan Tulak
2015-07-21 12:39 ` Jan Tulak
2015-07-26 16:25 ` Christoph Hellwig
2015-08-03 10:40 ` Jan Tulak
2015-08-03 17:20 ` Eric Sandeen
2015-08-04 15:30 ` Jan Tulak [this message]
2015-08-04 16:24 ` Eric Sandeen
2015-08-06 13:13 ` Jan Tulak
2015-08-11 16:40 ` Jan Tulak
2015-07-26 16:28 ` Christoph Hellwig
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=1050814645.2742881.1438702230663.JavaMail.zimbra@redhat.com \
--to=jtulak@redhat.com \
--cc=hch@infradead.org \
--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