| 1 |
On Saturday 28 June 2014 09:15:47 Dale wrote: |
| 2 |
> > Alan McKinnon wrote: |
| 3 |
--->8 |
| 4 |
> >> But that's not your main problem. You got those filenames because the |
| 5 |
> >> source disk somehow has a problem and the names couldn't be read |
| 6 |
> >> properly. So junk was used instead. |
| 7 |
|
| 8 |
I thought it was more like: the file lister didn't recognise those bytes as |
| 9 |
valid characters so it printed a question-mark for each of them. If it is so, |
| 10 |
it's no use Dale looking for files with question-marks in their names. |
| 11 |
|
| 12 |
--->8 |
| 13 |
|
| 14 |
> It listed some files with a question mark in it but not the ones I am |
| 15 |
> looking for. So, is it possible that since it couldn't read the file it |
| 16 |
> just skipped them? |
| 17 |
|
| 18 |
It may not be true that it couldn't read the files; it just couldn't translate |
| 19 |
their names into text characters. The names are not held in the files whose |
| 20 |
names they are but somewhere in the inode structure. Someone with better |
| 21 |
knowledge of this (i.e.any at all) will have to explain what goes wrong if |
| 22 |
bytes on the disk adjacent to the file names get damaged along with the names. |
| 23 |
|
| 24 |
> I used rsync to do the copy instead of cp. Maybe that is it or otherwise, I |
| 25 |
> have a ton of directories to go diggin in to find them since it isn't the |
| 26 |
> one I thought it was. |
| 27 |
|
| 28 |
Do you know any characters in those dodgy names, Dale? If so, you may be able |
| 29 |
to use /usr/bin/find like so (hoping this isn't a grandma's egg - apologies if |
| 30 |
it is): |
| 31 |
|
| 32 |
find /path-to-files -iname \*known-part-of-name\* {} + |
| 33 |
|
| 34 |
-- |
| 35 |
Regards |
| 36 |
Peter |
Archives