From: Oleg Drokin <green@namesys.com>
To: Christian Kujau <evil@g-house.de>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: vpf-10680, minor corruptions
Date: Sat, 28 Jun 2003 13:58:47 +0400 [thread overview]
Message-ID: <20030628095847.GA19610@namesys.com> (raw)
In-Reply-To: <3EFCC72F.9020100@g-house.de>
Hello!
On Sat, Jun 28, 2003 at 12:37:35AM +0200, Christian Kujau wrote:
> >Well, the corruptions are different indeed.
> >Can you also publish debugreiserfs -d /dev/whateverdev
> >output (it is preferable that there would be new FS with only
> >one or two files written and immediately unmounted).
> i've done so, debugreiserfs-test.stdout is in ../reiserfs on the known
> 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.
Well, looking at this metadata dump, I cann reasonably assure you that
this dump was taken from fs that was written to without first applying
the patch I sent. (same block, zero, block, zero pattern in indirect items)
In other mails you write that now you see only some of files are differs
(as opposed to every file gets corrupted). Or may be there is a pattern
like "files less than 8k in size are uncorrupted and everything bigger
is corrupted"?
So can I look at the debugreiserfs -d output for the filesystm where
that happens (and I want to know filename of a corrupted file too).
My own alpha boot attempts are doomed it seems. the kernel I build on alpha itself
jumps to address zero before starting init. Hm. Or may be it is just unhappy with gcc 3.2.2,
time to build gcc 2.95.3 there, it seems.
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2003-06-28 9:58 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
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 ` Oleg Drokin [this message]
2003-06-28 11:23 ` vpf-10680, minor corruptions 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=20030628095847.GA19610@namesys.com \
--to=green@namesys.com \
--cc=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.