From: geoff@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 [thread overview]
Message-ID: <33b92a9c2d6b8da64f55409b1d7c1e76@collyer.net> (raw)
In-Reply-To: <5db02d8d4202afa28a05b7b943fbd553@terzarima.net>
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.
next prev parent reply other threads:[~2004-10-18 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 11:05 geoff
2004-10-17 11:18 ` Brantley Coile
2004-10-17 17:01 ` Russ Cox
2004-10-18 0:43 ` geoff
2004-10-18 8:03 ` Charles Forsyth
2004-10-18 8:24 ` geoff [this message]
2004-10-18 8:36 ` Charles Forsyth
2004-10-18 8:38 ` geoff
2004-10-17 17:35 ` boyd, rounin
2004-10-17 13:19 Aharon Robbins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33b92a9c2d6b8da64f55409b1d7c1e76@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).