All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Bruce Guenter <lists-reiserfs-list@bruce-guenter.dyndns.org>
Cc: reiserfs-list@namesys.com, vitaly@thebsh.namesys.com
Subject: Re: reiserfs tails and disk space
Date: Tue, 17 Jan 2006 10:58:13 -0800	[thread overview]
Message-ID: <43CD3E45.6080304@namesys.com> (raw)
In-Reply-To: <20060117181548.GB11010@untroubled.org>

The result is not expected, Vitaly please look into it.

Hans

Bruce Guenter wrote:

>Hi.
>
>I've been running a few tests with reiserfs and tails, and have been
>unable to create a setup where the use (or lack) of tails results in a
>significant difference in the amount of disk space used.
>
>Here's what I've done:
>
>1. Create a fresh 1GB filesystem (in a file on loopback), using reiserfs
>with no options.
>
>2. Mount the filesystem with either no options, "notail", "tails=off",
>"tails=on", or "tails=small".
>
>3. Unpack a sources tarball onto the filesystem, consisting of two fully
>compiled versions of the linux kernel.  The tarball contains 47996 files
>and 3321 directories totalling about 660MB of space.
>
>4. Measure the free disk space using df.
>
>5. Use dd to fill up the free disk space and count how many 1kB blocks
>it could write.
>
>In all of the tests, the result was within 12kB of each other.  In fact,
>the tests with "notail" or "tails=off" options had more usable disk
>space than when using tails.
>
>Results:
>
>Options    1K-blocks    Used Available
>default      1023964  645988  377976
>notail       1023964  645988  377976
>tails=off    1023964  645996  377968
>tails=on     1023964  646000  377964
>tails=small  1023964  645996  377968
>
>default      377600+0 records out
>notail       377600+0 records out
>tails=off    377592+0 records out
>tails=on     377588+0 records out
>tails=small  377592+0 records out
>
>I've put the log files and scripts up for review at
>	http://untroubled.org/reiserfsdf/
>I'm using Gentoo Linux, kernel 2.6.14-gentoo-r5
>
>Am I missing something, is this an expected result, or is something
>broken?
>
>Thanks.
>  
>


  reply	other threads:[~2006-01-17 18:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 18:15 reiserfs tails and disk space Bruce Guenter
2006-01-17 18:58 ` Hans Reiser [this message]
2006-01-18 18:34   ` Vitaly Fertman
2006-01-19 19:53     ` Bruce Guenter
2006-01-19 22:00       ` Vitaly Fertman
2006-01-21 18:08         ` Laurent Riffard

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=43CD3E45.6080304@namesys.com \
    --to=reiser@namesys.com \
    --cc=lists-reiserfs-list@bruce-guenter.dyndns.org \
    --cc=reiserfs-list@namesys.com \
    --cc=vitaly@thebsh.namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.