On Sun, Nov 7, 2010 at 4:38 PM, Engebakken Geir <geir.engebak...@edb.com> wrote: > I get the following error trying to synchronize a repository, thought it was > due to too few inodes in the file system, but a “df –i “ shows plenty of > inodes available :
> + svnsync synchronize file:///backup/java > > svnsync: Can't create directory > '/backup/java/db/transactions/54270-7d7v.txn': Too many links There is a maximum built into every operating system I know, to prevent an accidental recursive symlink or symlink loop from making the operating system descend *perpetually* down a directory tree and get seriously lost. This is similar to the limits on maximum directory depth, and maximum filename length: we don't notice them until we run into them, usually due to some other kind of mistake. Check each component of your path for symlinks. /back, /backup/java, /backup/java/db, etc., and see which is the problem. You should be able to replicate the problem by doing "ls -ld" on each relevant parent directory until one failes. Such problems are often exacerbated by people doing 'rsync' operations carelessly and accidentally mirroring symlinks inside of directoryes pointed to by other symlinks, instead of replacing the symlink. (This happened to a colleage last week.)
