From: Aharon Robbins <arnold@skeeve.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] truncation via wstat on ken's fs
Date: Sun, 17 Oct 2004 15:19:27 +0200 [thread overview]
Message-ID: <200410171319.i9HDJR7R025520@skeeve.com> (raw)
> > Changing the length is easy, but giving back the no-longer-needed
> > blocks is messy, involving a recursive walk of the indirect blocks.
> > I'm tempted to just change the length, which gives the desired
> > user-visible effect, unless the side-effect of freeing the
> > unneeded storage is important to someone.
>
> Leaving the blocks there was the first thing I thought of.
> They will get reclaimed when the file is deleted anyway.
> Seems like a good idea to me.
Who says the file will ever get deleted?
Arnold
next reply other threads:[~2004-10-17 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 13:19 Aharon Robbins [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2004-10-18 8:36 ` Charles Forsyth
2004-10-18 8:38 ` geoff
2004-10-17 17:35 ` boyd, rounin
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=200410171319.i9HDJR7R025520@skeeve.com \
--to=arnold@skeeve.com \
--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).