rra at stanford.edu
Mon Apr 10 09:19:01 UTC 2000
Pawel Krawczyk <kravietz at ceti.pl> writes:
> Hello, I've had some problems with INN-2.2.2 on Linux 2.2.14 with
> ReiserFS partition. The filesystem is in beta and I've reported this to
> its developers, and they said it's a bug in INN. Please see the attached
> messages for full story. Please feel free to ask me if you need any
> additional details or tests. Thanks in advance.
Hm. I've not seen this report before.
> From: kravietz at ceti.pl (Pawel Krawczyk)
> Our w3cache & news server was running 2.2.14/3.5.15 so far with Rupasov
> hash enabled, on over 11 GB of diskspace.
> Today I've decided to upgrade to 3.5.16 and after installing new kernel
> I've got some problems with INN which got crazy on messed up article
> numbers, which became in effect out of synchronization with the active
> file. I've got lots 'file exists' errors in INN log file, when it
> attempted to symlink articles to names it thought were unused.
> From: reiser at idiom.com (Hans Reiser)
> Subject: Re: (reiserfs) possible problem with Rupasov hash?
> Date: 17 Jan 2000 17:00:06 +0100
> X-Cc: reiserfs at devlinux.com
> This is an INN programming bug which ext2 covers over. It involves
> mallocing and assuming the the byte after the malloc'd memory will be 0.
Could you give me some more details on where this is or some more
information on how we can find it and get it fixed? Thanks!
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the inn-bugs