From: Christian Kujau <evil@g-house.de>
To: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: vpf-10680, minor corruptions
Date: Sat, 28 Jun 2003 01:01:42 +0200 [thread overview]
Message-ID: <3EFCCCD6.4000807@g-house.de> (raw)
In-Reply-To: <3EFCC72F.9020100@g-house.de>
Christian Kujau schrieb:
> address. let me repeat, that not _all_ files in the fs are corrupted.
> the two textfiles i have just written into the newly created reiserfs
> are _not_ different from their origins. however, when i copy many files,
> a certain amount of files get corrupted.
>
that said, i've done some testings (yes, i really have time-> holidays!)
to find out the amount of files triggering the corruptions. started with
10, 20, 200 (text)files gave me _no_ corruptions. i was already about
doubting myself, that i copied again my /lib to the fresh fs:
lila:~# mount -o loop test.img /mnt/bench/
lila:~# /bin/cp -a /lib/ /mnt/bench/
lila:~# find /lib/ | wc -l
475
lila:~# diff -r /lib/ /mnt/bench/lib/ | wc -l
diff: /lib/modules/2.5.65/build: No such file or directory
diff: /mnt/bench/lib/modules/2.5.65/build: No such file or directory
diff: /lib/modules/2.5.69/build: No such file or directory
diff: /mnt/bench/lib/modules/2.5.69/build: No such file or directory
diff: /lib/modules/2.5.70/build: No such file or directory
diff: /mnt/bench/lib/modules/2.5.70/build: No such file or directory
168
lila:~#
(the warnings are ok, these are correct dead links.)
so, it's 168 out of 475--> 35%. but i still don't know the exact amount
of file needed to get a corruption. (even with 200 files i should get 70
corruptions...)
if that would be important/helpful i could do further tests...
Christian.
next prev parent reply other threads:[~2003-06-27 23:01 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 14:45 vpf-10680, minor corruptions Christian Kujau
2003-06-18 15:26 ` Oleg Drokin
2003-06-18 18:01 ` Christian Kujau
2003-06-19 5:45 ` Oleg Drokin
2003-06-19 18:55 ` vpf-10680, minor corruptions -- oooh! Christian Kujau
2003-06-20 11:42 ` Christian Kujau
2003-06-20 12:29 ` Oleg Drokin
2003-06-20 14:14 ` Christian Kujau
2003-06-20 22:43 ` vpf-10680 corruptions Christian Kujau
2003-06-21 10:37 ` Christian Kujau
2003-06-21 10:41 ` Oleg Drokin
2003-06-21 10:44 ` Christian Kujau
2003-06-23 7:38 ` vpf-10680, minor corruptions Hans Reiser
2003-06-23 9:02 ` Oleg Drokin
2003-06-23 9:28 ` Hans Reiser
2003-06-23 13:38 ` Christian Kujau
2003-06-24 13:19 ` Oleg Drokin
[not found] ` <3EF86928.7080504@g-house.de>
[not found] ` <20030624151940.GC21845@namesys.com>
2003-06-24 17:21 ` Christian Kujau
2003-06-25 0:42 ` Christian Kujau
2003-06-25 5:40 ` Oleg Drokin
2003-06-25 13:17 ` Christian Kujau
2003-06-25 18:26 ` Christian Kujau
2003-06-26 6:35 ` Oleg Drokin
2003-06-26 9:26 ` Oleg Drokin
2003-06-26 12:38 ` Christian Kujau
2003-06-27 9:28 ` Oleg Drokin
2003-06-27 12:18 ` Christian Kujau
2003-06-27 12:25 ` Oleg Drokin
2003-06-27 12:32 ` Christian Kujau
2003-06-27 12:38 ` Oleg Drokin
2003-06-27 16:13 ` Oleg Drokin
2003-06-27 16:23 ` Chris Mason
2003-06-27 17:34 ` Oleg Drokin
2003-06-27 16:33 ` Christian Kujau
2003-06-27 16:33 ` Christian Kujau
2003-06-27 19:20 ` Christian Kujau
2003-06-27 21:14 ` Oleg Drokin
2003-06-27 22:37 ` Christian Kujau
2003-06-27 23:01 ` Christian Kujau [this message]
2003-06-27 23:01 ` Christian Kujau
2003-06-27 23:02 ` Christian Kujau
2003-06-28 0:24 ` vpf-10680, minor corruptions (sorry) Christian Kujau
2003-06-28 9:58 ` vpf-10680, minor corruptions Oleg Drokin
2003-06-28 11:23 ` Christian Kujau
2003-06-28 12:09 ` Oleg Drokin
2003-06-28 11:45 ` Christian Kujau
2003-06-28 11:53 ` Oleg Drokin
2003-06-28 11:59 ` Christian Kujau
2003-06-28 12:15 ` Christian Kujau
2003-06-28 12:18 ` Oleg Drokin
2003-06-28 15:52 ` vpf-10680, minor corruptions (solved?) Christian Kujau
2003-06-29 8:54 ` Oleg Drokin
2003-06-30 0:31 ` vpf-10680, minor corruptions (solved!) Christian Kujau
2003-06-30 5:31 ` Oleg Drokin
2003-06-26 6:28 ` vpf-10680, minor corruptions Oleg Drokin
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=3EFCCCD6.4000807@g-house.de \
--to=evil@g-house.de \
--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.