Reiserfs-3.6.25 (2.4.21) ., instead of .., rsync Q

Reiserfs-3.6.25 (2.4.21) ., instead of .., rsync Q

[Guennadi Liakhovetski]

Hello

After running a machine for some time I've got an empty directory with

ls -a /var/run/sudo/user/ showing
.  .,

and

ls -al /var/run/sudo/user/
ls: /var/run/sudo/user/.,: No such file or directory
total 1
drwx------    2 root     root           48 Jan  1  1985 .

Hm, and the date above doesn't seem right too:-) S.M.A.R.T. didn't record
any errors on the disk.

Don't know if this would be of much help, though - I've already removed
the directory (rmdir worked ok), I had to do a backup, and with that
structure rsync couldn't go further.

BTW, unrelated - does anyone happen to know if using up 300M virtual
memory, and even leading to OOM is ok for rsync, when sync-ing large
data-volumes (20Gb)?

Thanks
Guennadi
---
Guennadi Liakhovetski

Re: Reiserfs-3.6.25 (2.4.21) ., instead of .., rsync Q

[Oleg Drokin]

Hello!

Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:

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

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?

Bye,
    Oleg

Re: Reiserfs-3.6.25 (2.4.21) ., instead of .., rsync Q

[Guennadi Liakhovetski]

On Mon, 29 Dec 2003, Oleg Drokin wrote:

> 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
>
> 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

Re: Reiserfs-3.6.25 (2.4.21) ., instead of .., rsync Q

[Oleg Drokin]

Hello!

On Mon, Dec 29, 2003 at 07:05:06PM +0100, Guennadi Liakhovetski wrote:
> > 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.

> 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