I've been using Pim's version of rsync 2.5.5-vfdhack-1 and mp3tofid3.00 for some time.

Anyway, recently I restructured my mp3 directory a little bit. It now has 1 extra level :-

was /data/mp3/<artist>/album

now /data/mp3/<type>/<artists>/<album>

Anyway, my rsync on the empeg now has errors :-

readlink drive0/fids/_00011/fd0: Permission denied
readlink drive0/fids/_00011/fe0: Permission denied
readlink drive0/fids/_00011/ff0: Permission denied
readlink drive0/fids/_00012/000: Permission denied
readlink drive0/fids/_00012/010: Permission denied
readlink drive0/fids/_00012/020: Permission denied

Got 575 errors in fact.

Now a search on the web results in this being caused by MAXPATHLEN being exceeded. However, none of the pathnames are over 200 characters long. According to a little test I did, the empeg has MAXPATHLEN set to 4095.

From the source of rsync it seems to use MAXPATHLEN so that didn't look like the issue. Just to be sure I compiled it up myself with a printf for MAXPATHLEN and sure enough it printed out 4095.

So has anyone got any ideas?

Greetings!

At a guess, I would say that because you added the directory in the middle of the path, rsync is trying to verify the file and finds that the upper level path is no longer valid. I am guessing that "readlink" is that you have a symbolic link collection that points to the old directory structure, now broken.

Paul, thats not it. I completely rebuilt my mp3tofid database from scratch and also even resorted to running mke2fs on drive0 and drive1 to ensure that was empty as well.

Its a clean setup with a new mp3tofids database.

The issue is only with 575 files out of 12000. These are the longest named files as well, but as I said, none are over 200 bytes in length.

Any special characters or other similarities that make those files stand out?

Just the length. The artist/album/track name didn't change..

Although I''m not conviced about the length being the issue.

Only things that got moved this time have a problem. I moved all my J.K Rowling books a few weeks ago. It's also everything that was moved this time. All 571 files (my mistake earlier my error log had 4 extra lines of errors from rsync not readlink errors).

I've run chown/chmod on the mp3's and the symlinks that mp3tofids created (even though they were recreated). So something is just odd here

One thought - is the filesystem mounted read/write? Perhaps the resync is trying to syncronize and remove the old links. Can you try a dry run rsync (-n), post the results and see what it is trying to do? Maybe it is trying to delete or sync something you are not expecting.

Well as if by magic its all working now. I did another set of chown/chmod's and now everything is find. Guess permissions of some sort were wrong.

Just have to wait for the rsync's to finish now