Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269282AbUICGB3 (ORCPT ); Fri, 3 Sep 2004 02:01:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269002AbUICGB2 (ORCPT ); Fri, 3 Sep 2004 02:01:28 -0400 Received: from rwcrmhc11.comcast.net ([204.127.198.35]:24768 "EHLO rwcrmhc11.comcast.net") by vger.kernel.org with ESMTP id S269282AbUICGAu (ORCPT ); Fri, 3 Sep 2004 02:00:50 -0400 Message-ID: <41380854.3020607@namesys.com> Date: Thu, 02 Sep 2004 22:59:48 -0700 From: Hans Reiser User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Masover CC: Spam , "Martin J. Bligh" , Linus Torvalds , Jamie Lokier , Horst von Brand , Adrian Bunk , viro@parcelfarce.linux.theplanet.co.uk, Christoph Hellwig , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Alexander Lyamin aka FLX , ReiserFS List Subject: Re: The argument for fs assistance in handling archives References: <20040826150202.GE5733@mail.shareable.org> <200408282314.i7SNErYv003270@localhost.localdomain> <20040901200806.GC31934@mail.shareable.org> <20040902002431.GN31934@mail.shareable.org> <413694E6.7010606@slaphack.com> <4136A14E.9010303@slaphack.com> <4136C876.5010806@namesys.com> <4136E0B6.4000705@namesys.com> <14260000.1094149320@flay> <4137BDA7.4040304@slaphack.com> <793789713.20040903024629@tnonline.net> <4137CA17.6060605@slaphack.com> In-Reply-To: <4137CA17.6060605@slaphack.com> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1432 Lines: 39 David Masover wrote: > Spam wrote: > [...] > |> I thought reiser4 had its journaling and atomic commits. Am I > |> mistaken? I run reiser4 as primary fs on my test systems and it seem > |> to work as expected. > > consider this: > > save_file () { > write() /* what if the write flushes halfway through > * then crashes? reiser4 does protect from this. reiserfs v3 does not. > */ > > blah() /* what if "blah" crashes? */ > write() > } > > Some apps need consistency across multiple files, but we don't even have > it on a single file. You need a new interface to do that. As you can > see, reiser4 has absolutely no way of knowing, anywhere in the above > code, when you're done writing -- and when the file is consistent. > > AFAIK, all that has to be done now for this to work is for them to > finish the userland interface to the journalling and atomic commits that > already exist for kernel space. But so far, all that is truly atomic is > metadata operations -- chmod, mv, mkdir, touch, and rm/rmdir are all > atomic, so long as you only use them on a single file/dir. But this has > been true in reiserfs3, xfs, ext3, and others. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/