archive mirror
 help / color / mirror / Atom feed
From: Eli Carter <>
Subject: .truncate function in filesystems
Date: Fri, 11 Jul 2003 14:52:38 -0500	[thread overview]
Message-ID: <> (raw)


I'm rather at a loss to understand what .truncate is supposed to do when 
it _extends_ a file (2.5.68+ kernel).  Looking through the examples in 
the tree, I don't see where they deal with that case.  Could someone 
give me a clue as to how .truncate is supposed to...tell the kernel what 
blocks it is to use when it goes to read from the extended portion of 
the file?

So far, I have googled, grep'ed, looked at, started in on, emailed linux-fsdevel and kernel-newbies...  and I'm 
still not getting anywhere.  Even a basic explanation of how filesystems 
  deal/interact with buffer heads and inodes would probably help at this 

Any clues or pointers or _anything_ would be very much appreciated. :/

--------------------. "If it ain't broke now,
Eli Carter           \                  it will be soon." -- crypto-gram
eli.carter(a) `-------------------------------------------------

                 reply	other threads:[~2003-07-11 19:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).