In message <a238daae4e.tim@xxxxxxxxxxxxxxxxxxxxx> Tim Powys-Lybbe <tim@xxxxxxxxx> wrote: > In message of 1 Feb, Steven Pampling <steve.pampling@xxxxxxxxxxxxx> wrote: > > > On 01 Feb, Tim Powys-Lybbe <tim@xxxxxxxxx> wrote: > > > In message of 31 Jan, Steven Pampling <steve.pampling@xxxxxxxxxxxxx> > > > wrote: > > > > > > On 31 Jan, Tim Powys-Lybbe <tim@xxxxxxxxx> wrote: > > > > > > > > > It is perplexing as the copy command (the snipped part) had been set > > > > > to Force the copy. It is also perplexing as it means that COPY is > > > > > incapable of actually ... copying. > > > > > > > > Except that you mentioned that the file effectively involved an image > > > > filing system (the zip) and as such you are asking it to copy a file > > > > over a directory. > > > > > If it recognises that the item copied is a file, then it should > > > recognise that the destination is also a file: both have the same name > > > and filetype. (Or if one is a directory, then so is the other.) > > > > As per Martins answer - if it is a zip and SparkFS is loaded it is both a > > file and a directory. > > Of course. > > But it is the same object on both discs. When the copy command looks at > one it says it is a file and when the same command looks at the other it > says it is a directory. This is inconsistent - and is what I am trying > to point out. If there was no such inconsistency, copying could proceed > satisfactorily and my backups likewise. Do you have SparkFS running on one machine but not on the other? Dave --- To alter your preferences or leave the group, visit //www.freelists.org/list/iyonix-support Other info via //www.freelists.org/webpage/iyonix-support