All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zarochentsev <zam@namesys.com>
To: " Marc A. Lehmann " <pcg@goof.com>
Cc: reiserfs-list@namesys.com, stefan@hello-penguin.com
Subject: Re: Congratulations! we have got hash function screwed up
Date: Thu, 6 Jan 2005 15:45:06 +0300	[thread overview]
Message-ID: <20050106124505.GE5352@backtop.namesys.com> (raw)
In-Reply-To: <20041228221218.GA6412@schmorp.de>

Hello,

On Tue, Dec 28, 2004 at 11:12:18PM +0100,  Marc A. Lehmann  wrote:
> Hi!
> 
> When trying to upgrade or reinstall the xfonts-75dpi,
> xfonts-75dpi-transcoded or 100dpi & transcoded debian packages on my
> 2.6.10-rc3 amd64 reiserfsv3 host, I get the following errors:
> 
>    dpkg: error processing
>    /var/cache/apt/archives/xfonts-75dpi_4.3.0.dfsg.1-10_all.deb (--unpack):
>     unable to make backup link of
>     `./usr/X11R6/lib/X11/fonts/75dpi/lutBS19-ISO8859-1.pcf.gz' before
>     installing new version: Device or resource busy
>     dpkg-deb: subprocess paste killed by signal (Broken pipe)
>    Preparing to replace xfonts-75dpi-transcoded 4.3.0.dfsg.1-10 (using
>          .../xfonts-75dpi-transcoded_4.3.0.dfsg.1-10_all.deb) ...
>    dpkg: error processing /var/cache/apt/archives/xfonts-75dpi-transcoded_4.3.0.dfsg.1-10_all.deb (--unpack):
>     unable to make backup link of `./usr/X11R6/lib/X11/fonts/75dpi/lutBS19-ISO8859-10.pcf.gz' before installing new version: Device or resource busy
>    dpkg-deb: subprocess paste killed by signal (Broken pipe)
>    Errors were encountered while processing:
>     /var/cache/apt/archives/xfonts-75dpi_4.3.0.dfsg.1-10_all.deb
>     /var/cache/apt/archives/xfonts-75dpi-transcoded_4.3.0.dfsg.1-10_all.deb
> 
> And at the same time, I get this in my kernel log:
> 
>    ReiserFS: hdg2: warning: reiserfs_add_entry: Congratulations! we have got hash function screwed up
> 
> Sure sounds like a filesystem bug to me. Is this 2.6.10-rc3-specific or a
> generic bug in handling hash collisions?

Tea hash is designed to be more resistant.  

there is a generic problem with overloading of the generation counter, but
tea hash should mix file names better and have less chances to 'screw the hash
function up'.  

Does the debian install all X font files into one dir? May be you have your own
font files installed in the same dir? I suggest to split the dir into several
ones.

> Deleteing the fonts and installing the package works, but the next upgrade
> makes the error appear again.
> 
> -- 
>                 The choice of a
>       -----==-     _GNU_
>       ----==-- _       generation     Marc Lehmann
>       ---==---(_)__  __ ____  __      pcg@goof.com
>       --==---/ / _ \/ // /\ \/ /      http://schmorp.de/
>       -=====/_/_//_/\_,_/ /_/\_\      XX11-RIPE

-- 
Alex.

  parent reply	other threads:[~2005-01-06 12:45 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 22:12 Congratulations! we have got hash function screwed up Lehmann 
2004-12-29 18:55 ` Stefan Traby
2004-12-29 21:04   ` Lehmann 
2004-12-29 21:05   ` Hans Reiser
2004-12-29 21:43     ` Lehmann 
2004-12-29 21:46       ` Christian Iversen
2004-12-29 22:27         ` Lehmann 
2004-12-30  2:05       ` Hans Reiser
2004-12-30 10:22         ` Matthias Andree
2004-12-30 17:02         ` Lehmann 
2005-01-06 12:45 ` Alex Zarochentsev [this message]
2005-01-06 14:27   ` Lehmann 
2005-01-06 15:56     ` Hans Reiser
2005-01-06 16:13       ` Spam
2005-01-06 16:26         ` Chris Dukes
2005-01-06 16:29           ` Spam
2005-01-06 16:56             ` Chris Dukes
2005-01-07 17:22           ` Hans Reiser
2005-01-07 17:28             ` Chris Dukes
2005-01-07 23:27             ` flush earlier? (was Re: Congratulations! we have got hash function screwed up) David Masover
2005-01-07 23:52               ` Hans Reiser
2005-01-08  5:03                 ` David Masover
2005-01-08 20:48                   ` Hans Reiser
2005-01-09 23:26                     ` David Masover
2005-01-06 18:55     ` Congratulations! we have got hash function screwed up Edward Shishkin
2005-01-07 17:26       ` Lehmann 
  -- strict thread matches above, loose matches on Subject: below --
2004-12-30 11:52 Yiannis Mavroukakis
2004-12-30 12:40 ` Matthias Andree
2004-12-30 12:59   ` Cal
2004-12-30 14:18     ` Matthias Andree
2004-12-30 16:40       ` Hans Reiser
2004-12-30 16:51         ` Matthias Andree
2005-01-18 21:17         ` Grzegorz Jaśkiewicz
2005-01-19 16:06           ` Hans Reiser
2005-01-19 22:41             ` David Masover
2005-01-20 13:18             ` Edward Shishkin
2005-01-20 23:43               ` Grzegorz Jaśkiewicz
2005-01-21  9:31                 ` Edward Shishkin
2004-12-30 17:07       ` Esben Stien
2004-12-30 17:15         ` Christian Iversen
2004-12-30 17:47         ` Sander
2004-12-30 17:59           ` Esben Stien
2004-12-30 18:30             ` Sander
2004-12-30 18:46               ` Esben Stien
2004-12-30 18:49                 ` Chris Dukes
2004-12-30 19:21                 ` Sander
2004-12-30 19:29                   ` Esben Stien
2004-12-30 18:16           ` Esben Stien
2004-12-30 18:26           ` Spam
2004-12-30 20:41             ` Tom Vier
2004-12-30 23:14             ` Matthias Andree
2004-12-30 23:25               ` Spam
2004-12-31  4:11               ` Hans Reiser
2004-12-31  8:36                 ` Matthias Andree
2004-12-30 20:08         ` Hans Reiser
2004-12-30 21:55           ` Esben Stien
2004-12-31  4:05           ` David Masover
2004-12-31  4:26             ` Hans Reiser
2004-12-31  5:59               ` David Masover
2004-12-30 20:57         ` Adrian Ulrich
2004-12-30 21:01           ` Stefan Traby
2004-12-30 21:20             ` brianmas
2004-12-30 17:09 ` Lehmann 
2004-12-30 20:11   ` Hans Reiser
2004-12-30 13:24 Yiannis Mavroukakis
2004-12-30 14:11 ` Matthias Andree
2004-12-30 17:22 Yiannis Mavroukakis
2004-12-30 18:16 Burnes, James
2004-12-30 18:36 ` Esben Stien
2004-12-30 19:26   ` Matthias Andree
2004-12-30 19:24 ` Matthias Andree
2004-12-30 20:25 ` Hans Reiser

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=20050106124505.GE5352@backtop.namesys.com \
    --to=zam@namesys.com \
    --cc=pcg@goof.com \
    --cc=reiserfs-list@namesys.com \
    --cc=stefan@hello-penguin.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.