From: Gabor HALASZ <halasz.g@freemail.hu>
To: reiserfs-list@namesys.com
Subject: we have got hash function screwed up
Date: Mon, 05 Sep 2005 18:34:23 +0200 [thread overview]
Message-ID: <431C738F.4010803@freemail.hu> (raw)
Hi!
I got the next message:
Sep 5 17:48:32 sk8n kernel: ReiserFS: dm-10: warning:
reiserfs_add_entry: Congratulations! we have got hash function screwed up
Caused by:
17:47:43 Getting file
'main/x/xorg-x11/xserver-xorg-dbg_6.8.2.dfsg.1-6_i386.deb' size = 21256772
17:48:32 Transfer rate: 423.79 kb/sec lastfile, 293.55 kb/sec overall
17:48:32 -- ERROR -- Creating temp file
'main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.deb' : Device or
resource busy
17:48:32 Retrieving file failed. Exiting.
The strange magic:
root@sk8n:~# touch
/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.dea
root@sk8n:~# touch
/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.deb
touch: cannot touch
`/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.deb':
Device or resource busy
root@sk8n:~# touch
/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.dec
root@sk8n:~# touch
/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.ded
root@sk8n:~# touch
/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.dee
root@sk8n:~# ls -la /home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.*
-rw-r--r-- 1 root root 0 2005-09-05 18:26
/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.dea
-rw-r--r-- 1 root root 0 2005-09-05 18:26
/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.dec
-rw-r--r-- 1 root root 0 2005-09-05 18:26
/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.ded
-rw-r--r-- 1 root root 0 2005-09-05 18:26
/home/ftpd/pub/debian/pool/main/x/xorg-x11/.in.xserver-xorg_6.8.2.dfsg.1-6_i386.dee
and I found same message in the kernel log:
Sep 5 18:26:38 sk8n kernel: ReiserFS: dm-10: warning:
reiserfs_add_entry: Congratulations! we have got hash function screwed up
The filsystem was clear at the last mount:
Sep 5 12:30:24 sk8n kernel: ReiserFS: dm-10: found reiserfs format
"3.6" with standard journal
Sep 5 12:30:24 sk8n kernel: ReiserFS: dm-10: using ordered data mode
Sep 5 12:30:24 sk8n kernel: ReiserFS: dm-10: journal params: device
dm-10, size 8192, journal first block 18, max trans len 1024, max batch
900, max commit age 30, max trans age 30
Sep 5 12:30:24 sk8n kernel: ReiserFS: dm-10: checking transaction log
(dm-10)
Sep 5 12:30:24 sk8n kernel: ReiserFS: dm-10: Using rupasov hash to sort
names
The system is x86-64 (Opteron), Debian Sid from amd64.debian.net, 2.6.13
kernel, but same with 2.6.12.5.
What can I do?!
--
Gabor HALASZ <halasz.g@freemail.hu>
next reply other threads:[~2005-09-05 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 16:34 Gabor HALASZ [this message]
2005-09-05 17:31 ` we have got hash function screwed up michael chang
2005-09-06 9:10 ` Vladimir V. Saveliev
[not found] ` <431D72C5.105@freemail.hu>
2005-09-06 12:06 ` Vladimir V. Saveliev
2005-09-05 17:51 ` Konstantin Münning
2005-09-06 11:23 ` Nikita Danilov
2005-09-10 15:36 ` evilninja
2005-09-11 3:00 ` Valdis.Kletnieks
2005-09-11 22:49 ` evilninja
2005-09-12 1:02 ` Valdis.Kletnieks
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=431C738F.4010803@freemail.hu \
--to=halasz.g@freemail.hu \
--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.