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
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
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
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
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:[EMAIL PROTECTED]:\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
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:[EMAIL PROTECTED]:\200r?\t': No such
file or directory
had the same problem, it is related to fsck which computes hashes the
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:[EMAIL PROTECTED]:\200r?\t': No such
file
or directory
had the same
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
On Thursday 14 October 2004 21:08, [EMAIL PROTECTED] 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: