Skip to main content
13 events
when toggle format what by license comment
S Mar 21, 2016 at 13:48 history suggested Mateusz Piotrowski CC BY-SA 3.0
Standardize title and add the `backup` tag
Mar 21, 2016 at 13:20 review Suggested edits
S Mar 21, 2016 at 13:48
Mar 24, 2011 at 19:35 vote accept ttsiodras
Mar 24, 2011 at 19:12 answer added Geeklab timeline score: 1
Mar 24, 2011 at 17:02 comment added ttsiodras Additional info: it turns out that some filenames use characters that appear greek, but ARE NOT! Look (I hope HTML accomodates them): ΒΑΣΕΩΝ ∆Ε∆ΟΜΕΝΩΩΝ.htm. Both the "Delta" and "Omega" are bad - I copied a "normal" UTF8 Omega next to the one in the original filename - that character looks like the greek omega, but is NOT the greek omega! The file was saved from the Web, so apparently some web page was written to use this "fake Greek" characters... hence why cp737 can't map them. Which leads us back to UTF-8 - only a full unicode set can safely accomodate everything... but doesn't work!
Mar 24, 2011 at 16:57 comment added ttsiodras Tried it - shows garbage instead of the filenames. With cp737 I see valid filenames - it's just that some of them have '?' in them, and suffer the 'vanish' fate (i.e. they are reported in the dir/dirent syscalls, but can't be opened)
Mar 24, 2011 at 16:56 comment added Majenko Could you use cp869 instead?
Mar 24, 2011 at 16:40 comment added ttsiodras There is a common thing - the files that rsync reports as vanished, are those that ls -l -raw shows as having at least one '?' in their names... Apparently some characters have no "cp737-equivalent" representation, hence the failure. The problem is that the utf-8 mapping, which can handle anything, leads to an infinite recursion in folder navigation...
Mar 24, 2011 at 16:21 comment added Majenko Ok, so we know that the UTF mapping is broken somewhere fundamental - so we can't use it. Now, can you identify what the files that vanish have in common? Is it a particular character or something?
Mar 24, 2011 at 16:05 comment added ttsiodras verified - not just rsync, but also "find /iso1" gets stuck as well. Truss again show getdirentries() called over and over.
Mar 24, 2011 at 14:38 comment added ttsiodras truss revealed that rsync is probably stuck asking for the same directory over and over: 200.223900400 getdirentries(0x5,0x800a2e000,0x1000,0x800a2d068,0x0,0x0) = 196 (0xc4) 200.224160040 getdirentries(0x5,0x800a2e000,0x1000,0x800a2d068,0x0,0x0) = 196 (0xc4) 200.224394880 getdirentries(0x5,0x800a2e000,0x1000,0x800a2d068,0x0,0x0) = 196 (0xc4)
Mar 24, 2011 at 13:40 comment added Majenko How about running truss on the process? truss -d -s 255 -p <pid> That will show you exactly what it's doing when it gets stuck - which system calls it's running and how long they take.
Mar 24, 2011 at 13:34 history asked ttsiodras CC BY-SA 2.5