From: Hans Reiser <reiser@namesys.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: Stefan Andersson <stefan@siwnet.net>, reiserfs-list@namesys.com
Subject: Re: Less disk space with reiser4?
Date: Mon, 11 Apr 2005 13:22:04 -0700 [thread overview]
Message-ID: <425ADC6C.8090209@namesys.com> (raw)
In-Reply-To: <20050411195253.GD6211@backtop.namesys.com>
Alex Zarochentsev wrote:
>On Mon, Apr 11, 2005 at 04:30:53PM +0200, Stefan Andersson wrote:
>
>
>>Hi,
>>
>>I have a disk array wich I used reiserfs(v3) on, and got 932G.
>>Now I started to test reiser4 on it and get less space, 886G.
>>
>>Is it suppose to be like this or is there something wrong?
>>
>>
>
>reiser4 reserves 5% of disk space.
>
>That is so because of delayed block allocation impelented in reiser4. Actual
>block allocation is done near the transaction commit, it means the allocation
>has to be reliable -- we can't return ENOSPC because the write(2) call when we
>could return an error was already completed successfully.
>
>The reserved space makes the allocation reliable because it covers possible
>insertions (and growing of the internal reiser4 tree) of new extent items
>insertions on a highly fragmented fs.
>
>
It also improves performance to ensure that at least 5% is free.
>
>
>>I'am using linux 2.6.11.4 and default settings for mkfs.reiser4 and
>>mkfs.reiserfs,
>>and reiser4 patch from 2.6.11-mm3.
>>
>>//Stetan
>>
>>
>>
>
>
>
next prev parent reply other threads:[~2005-04-11 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 14:30 Less disk space with reiser4? Stefan Andersson
2005-04-11 15:09 ` Łukasz Mierzwa
2005-04-11 19:52 ` Alex Zarochentsev
2005-04-11 20:22 ` Hans Reiser [this message]
2005-04-11 20:43 ` Chester R. Hosey
2005-04-12 0:57 ` David Masover
2005-04-13 12:51 ` Stefan Andersson
2005-04-13 13:04 ` Alex Zarochentsev
2005-04-13 13:41 ` Stefan Andersson
2005-04-13 18:32 ` Perry Kundert
2005-04-14 4:35 ` David Masover
2005-04-14 7:49 ` Alex Zarochentsev
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=425ADC6C.8090209@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=stefan@siwnet.net \
--cc=zam@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.