Reiserfs-3.6.25 (2.4.21) ., instead of .., rsync Q
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Oleg Drokin
GL> After running a machine for some time I've got an empty directory with GL> ls -a
/var/run/sudo/user/showing
GL> . .,Sounds like a single bit error to me.
GL> and
GL> ls -al/var/run/sudo/user/
GL> ls:/var/run/sudo/user/.,: No such file or directory
Quoted 7 lines
Sure, because only "." and ".." hash is calculated in a special way.
GL> Don't know if this would be of much help, though - I've already removed GL> the directory (rmdir worked ok), I had to do a backup, and with that GL> structure rsync couldn't go further.
What if you try to run memtest86 to see if you have good RAM?
Hm, you mean it would have gone after a reboot?... No, don't think I tried to reboot. And, as said above, the directory is gone, so, can't check. I did try to run the memtest at some point, once it did catch an error... Well, I guess, we can just archive this error-report for statistical purposes, but alone it hardly should raise any worries:-)
Thanks and regards
Guennadi
---
Guennadi Liakhovetski
Hello!
Quoted 5 lines · Guennadi Liakhovetski
Quoted 4 lines
GL> Don't know if this would be of much help, though - I've already removed GL> the directory (rmdir worked ok), I had to do a backup, and with that GL> structure rsync couldn't go further.
What if you try to run memtest86 to see if you have good RAM?Hm, you mean it would have gone after a reboot?... No, don't think I tried
Not necessary. Corrupted block might have been written to the disk as well.
Quoted 2 lines
to reboot. And, as said above, the directory is gone, so, can't check. I did try to run the memtest at some point, once it did catch an error...
Ah, so memtest gave an error. Then I am surprised you still run on that memory.
Bye,
Oleg