[prev in list] [next in list] [prev in thread] [next in thread]
List: reiserfs-devel
Subject: Re: problem with reiser4
From: Simon Raffeiner <sturmflut () lieberbiber ! de>
Date: 2005-03-13 15:29:16
Message-ID: 200503131629.29120.sturmflut () lieberbiber ! de
[Download RAW message or body]
One of the 2.6.10-mm kernels killed my Reiser4 Root Partition, yesterday a
2.6.11-mm one nearly killed a ReiserFS 3.6 partition. Luckily I was able to
recover it by rebooting with Kanotix and running reiserfsck. Did you try with
Kernel 2.6.9-mm1, it's the last kernel I am running that runs without
problems.
Am Sonntag, 13. März 2005 15:46 schrieb Łukasz Mierzwa:
> 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
[Attachment #3 (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic