Strange File System Corruption

[daniel3000]

Hello,

I'm running pdaXrom 1.1.0beta3 and seem to have a strange kind of file system corruption in the root fs (jffs).

if I do an ls / I get the output quoted below.

Any ideas where this could come from (I have not looked into the root directory for quite some days, so I have no idea what could have caused this)?
any ideas how to fix this? This is kind of suspicious (and annoying)!

Everything still seems to work fine, though. But for how long?

Thanks a lot
daniel

Code: [Select]

œèÿô
’ý=E¾­šD`ƒÛCô


Ÿèÿô
«¨ý=E¾­šD`ƒÛCô

X¢èÿô
â??
”–ý=E¾­šDbÆ’Ã
Cô

P !"¥èÿô
žQý=E¾­šDbƒÛCô

0#$%&'(¨èÿô
÷¾ý=E¾­šDbƒÛCô

`)*+,-.
%.*s%.*s
%s: : %s%s:%d: _mcleanup: gmon.out: %s
???out of memory
@$ì
@dþ
[SUID]
adm:x:4:adm,daemon
bin
bin:x:1:bin,daemon
calling fini: %s
closing file=%s; opencount == %u
control
daemon:x:2:bin,daemon
dev
dip:x:40:
disk:x:6:
etc
home
homeroot
kismet:x:500:
kmem:x:9:
lib
lp:x:7:daemon,lp
mem:x:8:
mmedia:x:17:users
mnt
naninfNANINF(nil)inity%H:%M%Y-%m-%d%s: %s
nobody:x:65534:
operator:x:11:
opt
ping  = sxx root.root
proc
rcmd: accept: %m
rcmd: getaddrinfo: %s
rcmd: socket: %m
root
sbin
shared object not open
su  = sxx root.root
sys:x:3:bin,adm
tmp
tty:x:5:
users:x:100:
usr
utmp:x:45:
uucp:x:14:uucp
var
wheel:x:10:
www:x:63:
¨

¨
q
ˆ$­ûpè!@¨ÃÿÿÿÿÿÿÿÿÀøä!@ã!@¤ªIqÃÿÿÿÿ0ÅÿÿÿÿÿÿÿÿHÅÿÿÿ
?¿Â¸Ã¤!@ã!@

큐!=;1E¸«E¸«E
 Ã¯ðñòóôõö÷øùúÃ?

큐!=;1E¸«E¸«E
 Ã¯ðñòóôõö÷øùúÃ?
q    
큐!=;1E¸«E¸«E
 Ã¯ðñòóôõö÷øùúÃ?
q    íAô
=E½­šDDX:Dô
ê

큐!=;1E¸«E¸«E
 Ã¯ðñòóôõö÷øùúÃ?
q    íAô
=E½­šDDX:Dô
ê
åíAô

큐!=;1E¸«E¸«E
 Ã¯ðñòóôõö÷øùúÃ?
q    íAô
=E½­šDDX:Dô
ê
åíAô
=E½­šDLX:Dô
ë
4åÿô
$E½­šD²‡ÛC
큐!=;1E¸«E¸«E
 Ã¯ðñòóôõö÷øùúÃ?
q    íAô
=E½­šDDX:Dô
ê
åíAô
=E½­šDLX:Dô
ë
4åÿô
$E½­šD²‡ÛCô

7夁Å¡Æ’=E    DøD    DøD
X
6789:;<=>?@AË.ñ­¤ô
¨
x=Etñ

[InSearchOf]

I had that happen before... that is when my backup nand came in handy....

Late

[bluedevils]

the format looks like it came from the /etc/group file or something similar.  Did you do a cp/mv of the group file to /?  Or for x in `cat /etc/group`;do mkdir /$x;done

[daniel3000]

well, not that I know of  

Thanks for the pointers. Yes, a NAND backup would come in handy, maybe I'll restore the latest one. But it is two weeks old, so this would mean quite a lot of work in order to restore a lot of new settings.
This is why I wanted to avoid that...

Maybe there was an errorneous cut'n'paste action on the conole which indeed created these dirs/files in root. I have not seen something like that anywhere else yet.

I'l try to delete these things and go on until I encounter more of such problems.

daniel

[daniel3000]

okay, I was able to delete all the strange files (they were files, not directories) using mc. Now everything seems to be normal.