Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: RFC: deprecate mkfs.xfs protofile functionality
Date: Thu, 20 Dec 2018 08:02:51 -0800	[thread overview]
Message-ID: <20181220160251.GA27208@magnolia> (raw)
In-Reply-To: <e3b338cb-33d0-04d0-c14c-7b06a7b924c9@sandeen.net>

On Thu, Dec 20, 2018 at 08:34:25AM -0600, Eric Sandeen wrote:
> I'd like to deprecate and eventually remove the protofile functionality
> in mkfs.xfs, because it's not well tested code which is really a special
> snowflake in the codebase that adds complexity.  And as far as I know,
> nobody uses it.

It also would seem to barf out corrupt long format symlinks on v5
filesystems, as I discovered while cleaning up mkfs and repair
yesterday.

> If I'm wrong though, speak up now.  Is anybody using protofiles?
> 
> (If you don't know what a protofile is, then you're not using it.
> And let's not turn this into a "well I could think of a way to use it"
> discussion, because it's been there for a couple decades and if you're
> not using it /yet/ ... unless there really is some new usecase on the
> horizon which would clearly depend on it.)

I'd rather have a mkfs feature that copies everything under a given path
into a newly formatted filesystem, and even then only if there's an
especially good reason why mount/cp/umount cannot be done.

So I say nuke the protofiles in xfsprogs 5.0. :P

--D

> Thanks,
> -Eric

      reply	other threads:[~2018-12-20 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 14:34 RFC: deprecate mkfs.xfs protofile functionality Eric Sandeen
2018-12-20 16:02 ` Darrick J. Wong [this message]

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=20181220160251.GA27208@magnolia \
    --to=darrick.wong@oracle.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