mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Maria Short <mgolod@ieee.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux slack space question
Date: Mon, 11 Dec 2006 18:30:49 +0100	[thread overview]
Message-ID: <20061211173049.GD29778@harddisk-recovery.com> (raw)
In-Reply-To: <3c698a820612080921u20a957d9x1ac1e01e6734d025@mail.gmail.com>

On Fri, Dec 08, 2006 at 12:21:04PM -0500, Maria Short wrote:
> I have a question regarding how the Linux kernel handles slack space.
> I know that the ext3 filesystems typically use 1,2 or 4 KB blocks and
> if a file is not an even multiple of the block size then the last
> allocated block will not be completely filled, the remaining space is
> wasted as slack space.
> 
> What I need is the code in the kernel that does that. I have been
> looking at http://lxr.linux.no/source/fs/ext3/inode.c but I could not
> find the specific code for partially filling the last block and
> placing an EOF at the end, leaving the rest to slack space.

Think about it: what value would an EOF have if all byte values are
allowed in a file?

>From the very first Unix filesystem an inode contains both the number
of blocks it contains and the actual file size.

> Please forward the answer to mgolod@ieee.org as soon as possible.

Hmm no. You asked a public forum so the reply will go to that same
public forum. See http://catb.org/esr/faqs/smart-questions.html#noprivate .


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

      parent reply	other threads:[~2006-12-11 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 17:21 Maria Short
2006-12-08 17:46 ` Bob Copeland
2006-12-08 18:51 ` linux-os (Dick Johnson)
2006-12-11 17:30 ` Erik Mouw [this message]

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=20061211173049.GD29778@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgolod@ieee.org \
    /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

all inboxes | Powered by JetHome®