From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <2d26e403df2c03ed8e41e93d4bc64b2d@terzarima.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] truncation via wstat on ken's fs From: Charles Forsyth Date: Mon, 18 Oct 2004 09:36:05 +0100 In-Reply-To: <33b92a9c2d6b8da64f55409b1d7c1e76@collyer.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-wtgwbzekeygxdpqntvjdirvpgw" Topicbox-Message-UUID: efc617fc-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-wtgwbzekeygxdpqntvjdirvpgw Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit a bit further down in the same code is the real need for BSLOP: some pesky `--' in the wrong place, but i digress. even with the worm, it might depend how often files are created and destroyed between dumps (eg, big mailboxes rewritten), and meta-data writes are often forced through to the device i think. it really depends how accurate the comment is, and whether it does indeed make any detectable difference now! --upas-wtgwbzekeygxdpqntvjdirvpgw Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by lavoro; Mon Oct 18 09:26:27 BST 2004 Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id BD83163AF7 for ; Mon, 18 Oct 2004 04:24:23 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id AB5F431EB6 for <9fans@cse.psu.edu>; Mon, 18 Oct 2004 04:24:09 -0400 (EDT) Received: from mail.cse.psu.edu ([127.0.0.1]) by localhost (psuvax1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18496-02-12 for <9fans@cse.psu.edu>; Mon, 18 Oct 2004 04:24:07 -0400 (EDT) Received: from collyer.net (xtc.collyer.net [216.240.55.168]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id C2DEE31EB3 for <9fans@cse.psu.edu>; Mon, 18 Oct 2004 04:24:06 -0400 (EDT) Message-ID: <33b92a9c2d6b8da64f55409b1d7c1e76@collyer.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] truncation via wstat on ken's fs Date: Mon, 18 Oct 2004 01:24:04 -0700 From: geoff@collyer.net In-Reply-To: <5db02d8d4202afa28a05b7b943fbd553@terzarima.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+forsyth=terzarima.net@cse.psu.edu Errors-To: 9fans-bounces+forsyth=terzarima.net@cse.psu.edu I was just looking at that very comment. It shouldn't matter for WORMs, since blocks are never reused. I wonder how much it matters for other file systems, given that one would expect to be serving from RAM cache most of the time. I note that fossil seems to just free the blocks in forward order. --upas-wtgwbzekeygxdpqntvjdirvpgw--