From: Michael Weissenbacher <webmaster@dermichi.com>
To: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: reiser4 - Non-removable files in lost+found
Date: Fri, 15 Oct 2004 10:11:27 +0200 [thread overview]
Message-ID: <416F862F.6010807@dermichi.com> (raw)
In-Reply-To: <416F855C.8040204@dermichi.com>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
Michael Weissenbacher wrote:
>> rm /lost+found/lost_name_*
>>
>> gives:
>>
>> rm: cannot remove `/lost+found/lost_name_5447b:6b68746d6c6361:27e2e2r?\t
>>
>> v\310:H\327\377\257O\275\275: v\310:\200r?\t@\001\261:\200r?\t': No such
>> file or directory
>
> had the same problem, it is related to fsck which computes hashes the
> wrong way if filenames are too long (and/or contain non-ascii
> characters). vladimir sent a patch to the mailing list that corrected
> this bug for me. not sure if this is already available in the
> pre-version of reiser4progs.
>
> regards,
> michael
>
here's the patch...
[-- Attachment #2: r5_hash.c.diff --]
[-- Type: text/x-patch, Size: 487 bytes --]
--- reiser4progs-1.0.0/plugin/hash/r5_hash/r5_hash.c.orig 2004-08-31 18:48:01.749889832 +0400
+++ reiser4progs-1.0.0/plugin/hash/r5_hash/r5_hash.c 2004-08-31 18:46:08.864051088 +0400
@@ -9,10 +9,12 @@
uint64_t r5_hash_build(char *name, uint32_t len) {
uint32_t i;
uint64_t a = 0;
+ unsigned char *uname;
+ uname = (unsigned char *)name;
for (i = 0; i < len; i++) {
- a += name[i] << 4;
- a += name[i] >> 4;
+ a += uname[i] << 4;
+ a += uname[i] >> 4;
a *= 11;
}
next prev parent reply other threads:[~2004-10-15 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 17:08 reiser4 - Non-removable files in lost+found frbiscani
2004-10-14 18:42 ` Vitaly Fertman
2004-10-15 8:07 ` Michael Weissenbacher
2004-10-15 8:11 ` Michael Weissenbacher [this message]
2004-10-15 12:29 ` Vitaly Fertman
-- strict thread matches above, loose matches on Subject: below --
2004-10-18 13:50 frbiscani
2004-10-18 16:30 ` Michael Weissenbacher
2004-10-18 16:41 ` Adrian Ulrich
2004-10-18 16:33 ` E.Gryaznova
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=416F862F.6010807@dermichi.com \
--to=webmaster@dermichi.com \
--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.