Re: FreeBSD and xfsprogs ?

[Dave Chinner <david@fromorbit.com>]

On Tue, Mar 27, 2018 at 11:48:29AM -0500, Eric Sandeen wrote:
> On 3/27/18 11:07 AM, Darrick J. Wong wrote:
> > [cc the xfsprogs maintainer]
> > [cc xfs list]
> 
> Yes, thanks.
> 
> > On Mon, Mar 26, 2018 at 12:57:55PM -0700, Conrad Meyer wrote:
> >> Yeah, someone broke the build recently via a base toolchain change or
> >> a ports framework/compiler change.  I don't think that changes
> >> anything.
> >>
> >> On Mon, Mar 26, 2018 at 12:53 PM, Cy Schubert <Cy.Schubert@cschubert.com> wrote:
> >>> In message <CAG6CVpU3qe10UUY6B-N4fs9WTwwUerVcJh0CrP22D8hvB4Z14Q@mail.gma
> >>> il.com>
> >>> , Conrad Meyer writes:
> >>>> On Fri, Mar 23, 2018 at 12:18 PM, Luis R. Rodriguez <mcgrof@kernel.org> wrote
> >>>> :
> >>>>> On the Linux xfs development list there is an RFC to remove IRIX,
> >>>>> Darwin, and FreeBSD support from xfsprogs, the userspace program used
> >>>>> to create/interact with XFS filesystems. Just wanted to poke and check
> >>>>> to ensure that FreeBSD is not interested in XFS, if this is incorrect
> >>>>> now would be the good time to chime into the list and discussion.
> >>>>>
> >>>>> [0] https://lkml.kernel.org/r/20180322202102.wpff347scdmfpv62@odin.usersys.
> >>>> redhat.com
> >>>>
> >>>> Hi Luis,
> >>>>
> >>>> FreeBSD 11+ can mount XFS filesystems read and write via a FUSE port
> >>>> incorporating LKL[0] (sysutils/fusefs-lkl).  I would appreciate
> > Yikes.  I'm curious, how many people use fusefs-lkl?
> > 
> > Eric will have more to say about this, but is your xfsprogs port still
> > on 3.2.4 because ./configure can't find libblkid?
> 
> So: At this point, it seems like if you're still on a 4 year old xfsprogs
> release with custom patches due to build problems we've never heard about,
> there doesn't seem to be a very strong effort to keep XFS on FreeBSD thriving.
> 
> And, given that you're stuck on 3.2.4, removing support from 4.16.0 won't
> change your situation anyway.
> 
> Are people using this?  Is anyone dedicated to maintaining it, or is it
> just kind of floating along at this point?
> 
> I'd rather not keep non-building freebsd code around just in case; I'd like
> to either see someone take ownership to get freebsd properly building upstream,
> or just drop it and let FreeBSD keep patching on the side as you've been doing
> for a few years anyway.
> 
> Thoughts?

We don't support fuse-lkl XFS filesystems on Linux, so I'm not sure
that using it on some other platform compels us to maintain a
current userspace tool port to those platforms...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com