From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Thomas Kuther <gimpel@sonnenkinder.org>
Cc: reiserfs-list@namesys.com
Subject: Re: journal size reiserfs vs reiser4
Date: Thu, 01 Sep 2005 16:53:32 +0400 [thread overview]
Message-ID: <4316F9CC.2090904@namesys.com> (raw)
In-Reply-To: <20050901144842.34629bcf@SiRiUS.home>
Hello
Thomas Kuther wrote:
> On Thu, 1 Sep 2005 13:46:04 +0200
> Thomas Kuther <gimpel@sonnenkinder.org> wrote:
>
>>Hello People!
>>
>>Just got a new harddrive and as i'm pretty pleased with reiser4 i
>>thought i'll make it reiser4. But then i realized that it uses almost
>>1/6 of the hd "for nothing"
>>
>>mkfs.reiser4 /dev/hde1:
>>/dev/hde1 reiser4 222G 7,5M 222G 1% /shared
>>
>>mkfs.reiserfs
>>/dev/hde1 reiserfs 233G 33M 233G 1% /shared
>>
>>somehow i had in mind that reiser4 should use much less space than
>>reiserfs, but it's exactly the other way round. Loosing 17GB of an
>>250GB disk is hard anyway. but loosing 28GB is simply no go.
>>
>>Now do i need to pass any special options to mkfs.reiser4 or why is
>>that? i'm using reiser4progs 1.0.4
>>
>>Thanks in advance
>>Tom
>
> OK found out one thing:
> Disk /dev/hde: 250.0 GB, 250059350016 bytes <-- crap!
>
> # echo "250059350016/1024/1024/1024" | bc
> 232
> ^^
> but that still doesn't explain why df only sees 222 when formatted with
> reiser4.
reiser4 reserves 5% of disk space for its internal needs.
next prev parent reply other threads:[~2005-09-01 12:53 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 11:46 journal size reiserfs vs reiser4 Thomas Kuther
2005-09-01 12:48 ` Thomas Kuther
2005-09-01 12:53 ` Vladimir V. Saveliev [this message]
2005-09-01 13:03 ` PFC
2005-09-01 13:12 ` Thomas Kuther
2005-09-01 13:05 ` Thomas Kuther
2005-09-01 13:07 ` Peter Staubach
2005-09-01 13:37 ` Vladimir V. Saveliev
2005-09-01 15:25 ` Hans Reiser
2005-09-01 16:06 ` Peter Staubach
2005-09-01 16:23 ` Marcel Hilzinger
2005-09-01 17:03 ` David Masover
2005-09-01 17:27 ` Hans Reiser
2005-09-01 17:36 ` Peter Staubach
2005-09-01 17:59 ` Hans Reiser
2005-09-01 18:14 ` Peter Staubach
2005-09-01 22:17 ` Hans Reiser
2005-09-02 2:28 ` michael chang
2005-09-02 6:34 ` Vladimir V. Saveliev
2005-09-02 7:19 ` Hans Reiser
2005-09-02 7:39 ` PFC
2005-09-02 16:02 ` michael chang
2005-09-02 17:37 ` Łukasz Mierzwa
2005-09-02 18:08 ` Gregory Maxwell
2005-09-02 21:29 ` Matt Stegman
2005-09-04 1:04 ` michael chang
2005-09-04 2:38 ` David Masover
2005-09-04 3:48 ` Hans Reiser
2005-09-04 9:29 ` Clemens Eisserer
2005-09-04 16:42 ` David Masover
2005-09-05 12:16 ` michael chang
2005-09-05 18:20 ` David Masover
2005-09-05 21:24 ` michael chang
2005-09-06 13:59 ` Tom Vier
2005-09-06 20:32 ` michael chang
2005-09-06 20:45 ` David Masover
2005-09-06 20:47 ` michael chang
2005-09-06 21:03 ` David Masover
2005-09-06 23:10 ` Hans Reiser
2005-09-07 2:48 ` Gregory Maxwell
2005-09-07 23:58 ` reiser4 merge status Hans Reiser
2005-09-08 0:08 ` Andrew Morton
2005-09-06 20:36 ` journal size reiserfs vs reiser4 Gregory Maxwell
2005-09-06 20:41 ` michael chang
2005-09-07 14:01 ` Tom Vier
2005-09-07 20:18 ` michael chang
2005-09-05 12:14 ` michael chang
2005-09-03 10:08 ` Sander
2005-09-03 11:34 ` Pierre Etchemaïté
2005-09-04 0:15 ` Hans Reiser
2005-09-01 13:13 ` Marcel Hilzinger
2005-09-01 13:15 ` Thomas Kuther
2005-09-01 14:08 ` michael chang
2005-09-01 13:13 ` Lexington Luthor
2005-09-01 13:28 ` Thomas Kuther
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=4316F9CC.2090904@namesys.com \
--to=vs@namesys.com \
--cc=gimpel@sonnenkinder.org \
--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.