From: Christian Kujau <evil@g-house.de>
To: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: vpf-10680, minor corruptions
Date: Fri, 27 Jun 2003 14:32:42 +0200 [thread overview]
Message-ID: <3EFC396A.7080808@g-house.de> (raw)
In-Reply-To: <20030627122556.GA8753@namesys.com>
Oleg Drokin schrieb:
> Sigh, I have found what happens. And it will happen on every 64 bit platform with recent 2.5 kernel.
> the internal reiserfs blocknumbers were referred to as 'unsigned long', that's where these
> extra blocks of zeroes are from, this also explains all other anomalies.
> Except when I make it 'unsigned int' as it ought to be, it still breaks,
> only in some other way which I have not understood yet.
> (yes, I seem to finally got our alpha to some working state and can do experiments locally now).
>
this sound like good news, yes? hm, but when you say on every 64bit
platform with recent 2.5 kernels, i wonder again where all the
sparc64/ppc64/opteron/itanium guys are to report corruptions...
compiling 2.5.72 with your patch is under way...
thank you Oleg,
Christian.
next prev parent reply other threads:[~2003-06-27 12:32 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 [this message]
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 ` 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=3EFC396A.7080808@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.