From: Hans Reiser <reiser@namesys.com>
To: Fred Schaettgen <kde.sch@ttgen.net>
Cc: reiserfs-list@namesys.com
Subject: Re: problem with reiser4
Date: Tue, 01 Mar 2005 14:06:31 -0800 [thread overview]
Message-ID: <4224E767.5030908@namesys.com> (raw)
In-Reply-To: <200503012007.53428.kde.sch@ttgen.net>
Fred Schaettgen wrote:
>On Tuesday 01 March 2005 19:54, fitzboy wrote:
>
>
>>Hello all,
>>I'm just switching from 2.4/reiser3 to 2.6/reiser4 on the first batch of
>>machines. We are running a bunch of apple xRAIDs connected to Dell
>>servers running Debian. we have the 2.6.10-mm kernel and we can make the
>>reiser4 partitions, but there is a lot of lost space somewhere. If I
>>create a reiser3 or xfs partition, I get 1.1T, but with reiser4 I can't
>>get above 984GB. That is too much of a jump to be explained by overhead,
>>so something is wrong... any thoughts?
>>
>>
>
>I'm not an expert, but isn't the free space just a a rough estimation?
>
Uh, no.
>You
>can't know in advance what the average file size will be etc. Maybe reiser4
>is just more conservative. What matters is how much data is actually stored
>on the disk the moment it runs full.
>
>
It is user error or a bug. He is saying the reported free space is
less, and this should not be. Note that it could be a units of
measurement issue also....
>Fred
>
>
>
next prev parent reply other threads:[~2005-03-01 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 18:54 problem with reiser4 fitzboy
2005-03-01 19:07 ` Fred Schaettgen
2005-03-01 22:06 ` Hans Reiser [this message]
2005-03-13 14:46 ` Łukasz Mierzwa
2005-03-13 15:29 ` Simon Raffeiner
2005-03-23 14:57 ` Łukasz Mierzwa
-- strict thread matches above, loose matches on Subject: below --
2005-12-15 23:40 Problem with Reiser4 Tobi Kunze
2005-12-15 23:46 ` Artur Makówka
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=4224E767.5030908@namesys.com \
--to=reiser@namesys.com \
--cc=kde.sch@ttgen.net \
--cc=reiserfs-list@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.