From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Steigerwald Subject: Re: Honest timeline for btrfsck Date: Wed, 12 Oct 2011 16:41:55 +0200 Message-ID: <201110121641.55974.Martin@lichtvoll.de> References: <4E8F1D38.7030202@snappymail.ca> <20111007192728.5e79f1e0@atmarama.noip.me> (sfid-20111007_195513_485840_ACEC3426) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 To: linux-btrfs@vger.kernel.org Return-path: In-Reply-To: <20111007192728.5e79f1e0@atmarama.noip.me> List-ID: Am Freitag, 7. Oktober 2011 schrieb Gour-Gadadhara Dasa: > On Fri, 07 Oct 2011 08:39:36 -0700 >=20 > Mike 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, n= ot >=20 > > the developers: > +1 Even if its a thousand +1 following, it seems to me that its perfectly=20 Chris Masons decision... Chris seems to have some ideas on when to release the fsck. So what do = you=20 think you achieve by asking for its release again and again? It won=B4t= =20 happen anytime sooner unless you happen to find the holy mantra that=20 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= =20 question the usefulness of repeating reminders. Chris Mason and other=20 developers possibly working on the fsck should know by now, that you wa= nt=20 it. So its unlikely that "I want it too" is going to change anything. Ciao, --=20 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html