reiser4 - Non-removable files in lost+found

reiser4 - Non-removable files in lost+found

[frbiscani]

After a reiser4 crash I had to run fsck with the --build-fs option. Some

garbage was collected in /lost+found. I deleted it for the most part, but

there are "files" I can't remove.

For example:

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
rm: cannot remove `/lost+found/lost_name_5447b:6b68746d6c6361:27e2f3r?\t

v\310:H\327\377\257O\275\275: v\310:\200r?\t@\001\261:\200r?\t': No such
file
or directory
rm: cannot remove `/lost+found/lost_name_5447b:6b68746d6c6361:27e306r?\t

v\310:H\327\377\257O\275\275: v\310:\200r?\t@\001\261:\200r?\t': No such
file
or directory
rm: cannot remove `/lost+found/lost_name_5447b:6b68746d6c6361:27e310r?\t

v\310:H\327\377\257O\275\275: v\310:\200r?\t@\001\261:\200r?\t': No such
file
or directory
[...]

and so on. I've tried also "rm -d" and unlink, but with no luck. Is there
a
way to clean up (apart from mkfs :))?

Thanks,

francesco


________________________________________
Crea la tshirt con il tuo nick! http://www.mediasetshop.it/JumpyChat/

Re: reiser4 - Non-removable files in lost+found

[Vitaly Fertman]

On Thursday 14 October 2004 21:08, frbiscani@jumpy.it wrote:
> After a reiser4 crash I had to run fsck with the --build-fs option. Some
>
> garbage was collected in /lost+found. I deleted it for the most part, but
>
> there are "files" I can't remove.
>
> For example:
>
> 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
> rm: cannot remove `/lost+found/lost_name_5447b:6b68746d6c6361:27e2f3r?\t
>
> v\310:H\327\377\257O\275\275: v\310:\200r?\t@\001\261:\200r?\t': No such
> file
> or directory
> rm: cannot remove `/lost+found/lost_name_5447b:6b68746d6c6361:27e306r?\t
>
> v\310:H\327\377\257O\275\275: v\310:\200r?\t@\001\261:\200r?\t': No such
> file
> or directory
> rm: cannot remove `/lost+found/lost_name_5447b:6b68746d6c6361:27e310r?\t
>
> v\310:H\327\377\257O\275\275: v\310:\200r?\t@\001\261:\200r?\t': No such
> file
> or directory
> [...]
>
> and so on. I've tried also "rm -d" and unlink, but with no luck. Is there
> a
> way to clean up (apart from mkfs :))?

would you pack the metadata with:
	debugfs.reiser4 -P /dev/xxx | bzip2 -c > xxx.bz2
and provide it to me for downloading?

-- 
Thanks,
Vitaly Fertman

Re: reiser4 - Non-removable files in lost+found

[Michael Weissenbacher]

> 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

Re: reiser4 - Non-removable files in lost+found

[Michael Weissenbacher]

[-- 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;
 	}
     

Re: reiser4 - Non-removable files in lost+found

[Vitaly Fertman]

On Friday 15 October 2004 12:07, 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.

yes, the fix is included into reiser4progs-1.0.2-pre1.

-- 
Thanks,
Vitaly Fertman

Re: reiser4 - Non-removable files in lost+found

[frbiscani]

Sorry for the mail-mess... I hate webmail :/

On Friday 15 October 2004 14:29, Vitaly Fertman wrote:
> On Friday 15 October 2004 12:07, Michael Weissenbacher wrote:
> >
> > 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.
>
> yes, the fix is included into reiser4progs-1.0.2-pre1.

Thank you all for the feedback. I installed reiser4progs-1.0.2-pre1 and
it
found the same number of corruptions as the number of undeletable files

in /lost+found. Should I run fsck with --build-fs then? Also, can this be

done when the partition is mounted read-only? I'm asking this because I
have to run reiser4progs from a chrooted environment where my / partition
is mounted read-only.

Thanks again,

  Francesco

________________________________________
Crea la tshirt con il tuo nick! http://www.mediasetshop.it/JumpyChat/

Re: reiser4 - Non-removable files in lost+found

[Michael Weissenbacher]

> in /lost+found. Should I run fsck with --build-fs then? Also, can this be
short answer: yes, this "renamed" the files in lost+found (in my case) 
so that i could delete them.

regards,
michael

Re: reiser4 - Non-removable files in lost+found

[E.Gryaznova]

Adrian Ulrich wrote:

>>Also, can this be done when the partition is mounted read-only? 
>>    
>>
>
>I did this some months ago and my kernel gave me a nice Oops ;-)
>
>Nikita told me on #reiser4 that it isn't possible to fsck a (ro)-mounted
>Filesystem..
>
>Maybe this changed and it's possible now..
>  
>
no, this does not work properly still.

Thanks,
Lena

>bye
>
>
>  
>

Re: reiser4 - Non-removable files in lost+found

[Adrian Ulrich]

> Also, can this be done when the partition is mounted read-only? 

I did this some months ago and my kernel gave me a nice Oops ;-)

Nikita told me on #reiser4 that it isn't possible to fsck a (ro)-mounted
Filesystem..

Maybe this changed and it's possible now..

bye