From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: rfc: drop support for historic fs formats from xfsprogs
Date: Wed, 8 Feb 2012 13:41:24 +1100 [thread overview]
Message-ID: <20120208024124.GB20305@dastard> (raw)
In-Reply-To: <20120207182902.GA22486@infradead.org>
On Tue, Feb 07, 2012 at 01:29:02PM -0500, Christoph Hellwig wrote:
> While doing a lot of xfs_repair work I noticed that there's a lot of
> effort spent on handling historic filesystem features. The two that
> make my life in repair hard are mostly:
>
> - unaligned inodes
> - dirv1
>
> none of which every made it to production on Linux. I'd like to suggest
> to drop support for old filesystem features before a certain cut off
> date after we release the currently pending xfsprogs 3.1.8 release.
That seems like a good idea to me - less code to support in future,
and I'd say taht code is rarely, if ever, tested to work these days.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-02-08 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 18:29 rfc: drop support for historic fs formats from xfsprogs Christoph Hellwig
2012-02-08 2:41 ` Dave Chinner [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=20120208024124.GB20305@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--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