On Saturday November 19, lfarkas@xxxxxxxxx wrote: > Neil Brown wrote: > > > The other is to use a filesystem that allows the problem to be avoided > > by making sure that the only blocks that can be corrupted are dead > > blocks. > > This could be done with a copy-on-write filesystem that knows about the > > raid5 geometry, and only ever writes to a stripe when no other blocks > > on the stripe contain live data. > > I've been working on a filesystem which does just this, and hope to > > have it available in a year or two (it is a back-ground 'hobby' > > project). > > why are you waiting so long? why not just release the project plan, and > any pre-pre-alpha code? that's the point of the cathedral and the > bazaar. may be others can help, find bugs, write code, etc.. Uhmm... maybe I'm just selfish and want to have all the fun to myself (it is as much a learning exercise as anything else)... or maybe I want to be a coder rather than a project manager... Despite the 'release early / release often' mantra, I think it is possible to release something too early. People look, find nothing there, lose interest and never come back. However I'm possibly at the stage were it might be worth making the project more visible... I'll think about it and let you know.... Thanks for your interest NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
