Hello!
On Tue, Aug 05, 2003 at 04:56:55PM +0400, Hans Reiser wrote:
rephrase that as, use 3.6.11, if it still fails, tell us, the segfault
will at least be fixed regardless of whether fsck has enough data to do
its job.
But it was not failing on the IDE drive anyway.
I don't understand
Hi
I'm really not a expert in this. I found the tip in:
http://www.unixwiz.net/techtips/recovering-ext2.html
Maybe it helps a bit
Do you mean that we could just miss
sync option and got wrong result? I will test it again.
Hello!
On Tue, Aug 05, 2003 at 04:28:15PM +0400, Hans Reiser wrote:
But while rebuilding the tree, I got a segmentation fault. Because I
didn't
want to continue work on the original raid system, I copied the entire
raid
disk to the IDE disk.
dd if=/dev/rd/c0d0 of=/dev/hda
On Tue, 08/05/03 at 23:08:31 +0200, Szakacsits Szabolcs wrote:
BTW, from your numbers it seems ext3 gives better overall performance.
That is an incorrect statement. Reiserfs is KNOWN to be heavier on CPU
than other filesystems, it's benefit is not there, it's benefit is in
speed of operation,
If dd without conv=noerror fails for you -- you have problems with
reading some blocks -- you should use dd_rescue instead as dd
forgets to create holes in the target image when cannot read some
block. This explains garbage in files in your case.
This same effect is available with normal
mozilla-1.5a.tar is mozilla 1.5alpha source tar, uncompressed.
Partition mkfs.ext3 or mkfs.reiser4 --keys=SHORT is run before each run.
Linux is 2.6.0-test2.
untar mozilla-1.5a.tar (file is on a reiser3 partition):
ext3: 17.64s 28% cpu
reiser4: 10.79s 67% cpu
sum: reiser4 0.61x time, 2.39x cpu
Szakacsits Szabolcs wrote:
How much memory you have? How big is mozilla-1.5a.tar? Did you include
'sync' in the tests? It seems reiser4 numbers are mostly in-memory
operations and not all data flushed to disk while this is apparently not
true for ext3. BTW, XFS numbers would be also/more
Grant Miner [EMAIL PROTECTED] wrote:
I tested the performace of various filesystems with a mozilla build tree
of 295MB, with primarily writing and copying operations. The test
system is Linux 2.6.0-test2, 512MB memory, 11531.85MB partition for
tests. Sync is run a few times throughout
