From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shawn Rutledge Subject: Re: where is the journal kept? Date: Tue, 16 Aug 2005 16:23:06 -0700 Message-ID: References: <20050815115310.GA28630@tranquility.scriptkitchen.com> <43009184.2080201@namesys.com> <200508150812.40382.pat@patdouble.com> <4300A603.2050602@namesys.com> <4300D240.7010109@namesys.com> <4302458E.9070604@namesys.com> <430268F4.8020100@slaphack.com> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <430268F4.8020100@slaphack.com> Content-Disposition: inline List-Id: Content-Type: text/plain; charset="us-ascii" To: David Masover Cc: reiserfs-list@namesys.com On 8/16/05, David Masover wrote: > Something Reiser4 does very well. If you have enough RAM, it's possible > to avoid any reads/writes at all -- given enough RAM, it behaves as a Well that's cool if it's true. But IMO for this application it ought to have a deadline - after the writes have been pending for 10 seconds or so, go ahead and commit all of them, in case I forget to unmount before I remove the card. > ramdisk, which is why I wish I knew how to tell Gentoo to *not* mount > tmpfs over /dev. >=20 > One other thing you might try is disabling the write-twice behavior. > Currently, if you've got a huge, fairly well-sorted file that you're > making lots of tiny writes to, such as a database, it makes sense to > write twice to keep the file from getting fragmented. But, > fragmentation isn't nearly as much an issue on truly random-access > media, so you'd want the default small-file behavior to be used > everywhere -- first write the data to the new location, then atomically > update the pointer to it as you deallocate the old location. What would you change to do that?