Re: Honest timeline for btrfsck

[Jeff Putney <jeffrey.putney@gmail.com>]

> Heh, what sort of "quality" are you thinking would develop? =A0A
> recovery tool by its nature is picking up the pieces where those
> pieces are inconsistent. =A0The nature of those inconsistencies will
> change with every patch that's more than a cleanup.
>

Seriously?  You want to delay the solving of the problems we have
today, because we are going to have different problems in the future?
I hate to be the bearer of bad news, but for the most part, we are
going to have new problems in addition to the ones we already have.
We are not going to get a whole brand new batch of problems that are
somehow going to magically make all our old problems obsolete.  You
also make the assumption that the solution to these new problems is
going to have absolutely no similarity to the current problems,
otherwise it would be beneficial to have a quality solution to similar
problems to build off of.

> Combined with the well-known tendencies of users to not report errors
> that are trivial to work around, and I find myself quite content with
> the status quo: =A0a few general recovery techniques that can be foun=
d
> with some digging, inconvenient enough that the reports don't get
> lost, with enough context that the appropriate warnings and
> alternatives can be given.

If the status quo is an acceptable condition, then you must not see
the need for any fsck utility.  If you see a need for an fsck utility,
then certainly you must see the problem in committing to 'eminently'
deliver that utility repeatedly for a year or so, and never delivering
it.  If you don't see that as a fundamental wrench in the works, I
don't know what would be.


> Yes, a deliberately broken-by-makefile version of what he's looking a=
t
> would be interesting, but I suspect it's not much past what any
> competent programmer would put together given a couple weeks going
> over the disk format, and we already have a couple of those.

Yeah, I am also suspicious that that is all that exists, and I suspect
that may have something to do with the resistance to releasing the
source.  If that is the case, why not just come clean about it, and
let others start contributing, so we can get somewhere with it.

> What we want is still in Chris' head, otherwise we _would_ have
> something.

If it is still only exists in his head, after a year, how long should
we wait before someone else takes the reigns?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html