All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Łukasz Mierzwa" <prymitive@o2.pl>
To: reiserfs-list@namesys.com
Subject: Re: problem with reiser4
Date: Sun, 13 Mar 2005 15:46:45 +0100	[thread overview]
Message-ID: <opsnkzb7igt3f2uk@localhost> (raw)
In-Reply-To: <4224BA6B.7040402@iparadigms.com>

Dnia Tue, 01 Mar 2005 10:54:35 -0800, fitzboy <fitzboy@iparadigms.com> napisa³:

> 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 got the same problem:

gremlin prymitive # mkfs.ext3 /dev/hdd5
mke2fs 1.35 (28-Feb-2004)
Etykieta systemu plików=
Typ OS: Linux
Rozmiar bloku=4096 (log=2)
Rozmiar fragmentu=4096 (log=2)
2562240 i-wêz³ów, 5120710 bloków
256035 bloków (5.00%) zarezerwowanych dla superu¿ytkownika
Pierwszy blok danych=0
157 grup bloków
32768 bloków w grupie, 32768 fragmentów w grupie
16320 i-wêz³ów w grupie
Kopie zapasowe superbloku zapisane w blokach:
         32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
         4096000

Zapis tablicy i-wêz³ów: zakoñczono
Tworzenie kroniki (8192 bloków): wykonano
Zapis superbloków i podsumowania systemu plików: wykonano

Ten system plików bêdzie automatycznie sprawdzany co ka¿de 24 montowañ
lub co 180 dni, zale¿nie co nast±pi pierwsze. Mo¿na to zmieniæ poprzez
tune2fs -c lub -i.

gremlin mnt # mount -t ext3 /dev/hdd5 /mnt/seagate/
gremlin mnt # df
System plików      bl. 1MB B        u¿yte dostêpne %u¿. zamont. na
/dev/hda1              69790MB   54438MB   15352MB  79% /
none                     262MB       0MB     262MB   0% /dev/shm
/dev/hdd5              20646MB      34MB   19563MB   1% /mnt/seagate
gremlin mnt # umount /mnt/seagate
gremlin mnt # mkfs.reiser4 /dev/hdd5
mkfs.reiser4 1.0.4
Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by reiser4progs/COPYING.

Block size 4096 will be used.
Linux 2.6.11-cko2 is detected.
Uuid 74aecbaf-6013-4b9f-9006-691d55f26940 will be used.
Reiser4 is going to be created on /dev/hdd5.
(Yes/No): Yes
Creating reiser4 on /dev/hdd5 ... done
gremlin mnt # mount -t reiser4 /dev/hdd5 /mnt/seagate/
gremlin mnt # df
System plików      bl. 1MB B        u¿yte dostêpne %u¿. zamont. na
/dev/hda1              69790MB   54438MB   15352MB  79% /
none                     262MB       0MB     262MB   0% /dev/shm
/dev/hdd5              19930MB       1MB   19930MB   1% /mnt/seagate

so it's 20646MB on ext3 versus 19930 with reiser4
I used reiser4progs 1.0.4 under 2.6.11-cko2 kernel

£ukasz Mierzwa

  parent reply	other threads:[~2005-03-13 14:46 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
2005-03-13 14:46 ` Łukasz Mierzwa [this message]
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=opsnkzb7igt3f2uk@localhost \
    --to=prymitive@o2.pl \
    --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.