Am Freitag, 7. Oktober 2011 schrieb Gour-Gadadhara Dasa: > On Fri, 07 Oct 2011 08:39:36 -0700 > > Mike <i...@snappymail.ca> wrote: > > I also don't think you are giving people enough credit. e2fsck will > > cause corruption pretty much everytime its run on a mounted file > > system, but a nice big nasty warning message seems to handle that > > quite well and anyone who ignores it, well thats their own fault, not > > > the developers: > +1
Even if its a thousand +1 following, it seems to me that its perfectly Chris Masons decision... Chris seems to have some ideas on when to release the fsck. So what do you think you achieve by asking for its release again and again? It won´t happen anytime sooner unless you happen to find the holy mantra that convinces Chris to release it now. I bet thats unlikely. So its either do an fsck for yourself or wait... BTRFS is still experimental software... I do not argue that having a nice fsck sooner than later is fine, but I question the usefulness of repeating reminders. Chris Mason and other developers possibly working on the fsck should know by now, that you want it. So its unlikely that "I want it too" is going to change anything. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
