Hi, I'm running rsync 2.5.6. I use it to backup a RH 7.3 file server (samba+appletalk) to a FAT32 external HD. I get the following output: .1e6prS failed: Invalid argumentsp_ind/Emails ind/.Icon .fJ98aa failed: Invalid argumentsp_ud/Emails ud/.Icon .qLRVCT failed: Invalid argumentkt/02_Tegninger/planer/ai/.Icon .zM65uw failed: Invalid argumentkt/02_Tegninger/planer/fmz/.Icon mkstemp 2001_12_Villa_OpNed/01_Korrespondance ind/01 Bygherre/Emails/.<None>.1.1.8sX6No failed: Invalid argument ... ... What exactly constitutes the bad argument here? I'd guess the dot-folder. Related question, I tried to use the same file for --exclude-from as I use with tar -X, and incidentally it appeared to work. I only keep some directory names in there, eg. .AppleDouble Temporary Items These are directories created by the client machines and rsync does not copy them to the destination. I tried to add .Icon in there and that did not work as expected (I still get the above error messages). Any idea why it would work for .AppleDouble but not .Icon? I know that it's "luck" that the same exclude file works and that I should try and use rsync exclude rules, but that doesn't explain .AppleDouble vs. .Icon. Thanks for any enlightenment, Morten
On Mon, Jun 30, 2003 at 09:42:57AM +0200, Morten Primdahl wrote:> > Hi, > > I'm running rsync 2.5.6. I use it to backup a RH 7.3 file server > (samba+appletalk) to a FAT32 external HD. I get the following output:Huh? What in the world are you doing? That description sounds very strange. I presume the RH box is the source, what is the rsync destination box, how does samba+appletalk get involved for a FAT32.> .1e6prS failed: Invalid argumentsp_ind/Emails ind/.Icon > .fJ98aa failed: Invalid argumentsp_ud/Emails ud/.Icon > .qLRVCT failed: Invalid argumentkt/02_Tegninger/planer/ai/.Icon > .zM65uw failed: Invalid argumentkt/02_Tegninger/planer/fmz/.IconThe above messages are garbage. Incomplete.> mkstemp 2001_12_Villa_OpNed/01_Korrespondance ind/01 > Bygherre/Emails/.<None>.1.1.8sX6No failed: Invalid argumentThis makes little sense. Are you sure you ran configure? One other thing. Don't allow line-wrapping of error messages.> ... > ... > > What exactly constitutes the bad argument here? I'd guess the > dot-folder.What "dot-folder"? If you are talking about the garbage lines and .Icon is a folder i know it isn't mkstemp that is the problem but there is no telling what is.> Related question, I tried to use the same file for --exclude-from as I > use with tar -X, and incidentally it appeared to work. I only keep some > directory names in there, eg. > > .AppleDouble > Temporary Items > > These are directories created by the client machines and rsync does not > copy them to the destination. I tried to add .Icon in there and that did > not work as expected (I still get the above error messages). Any idea > why it would work for .AppleDouble but not .Icon? I know that it's > "luck" that the same exclude file works and that I should try and use > rsync exclude rules, but that doesn't explain .AppleDouble vs. .Icon. > > Thanks for any enlightenment,-- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and Schmitt
On Wed, Jul 02, 2003 at 10:03:00AM +0200, Morten Primdahl wrote:> > >>Tried to enable -vvv but this makes rsync hang on the same file each > >>time: > > > > > > -vvv is known to cause hanging. It is, however the > > verbosity level needed to get some info out of that part of > > the code. Lets not try to debug the hang. Reduce the level one notch. > > Narrow the scope somewhat. And answer the questions asked in > > my previous email. > > I still get some garbage on stderr: > > .qsJ4iC failed: Invalid argumentsp_ind/Emails ind/.Icon > .klS8j3 failed: Invalid argumentsp_ud/Emails ud/.Icon > > The garbage lines only come for the .Icon folder.Is there actually a directory (we have no folders in UNIX/Linux filesystems) at the location indicated?> But also more valid messages like (still on stderr): > > mkstemp 2001_12_Villa_OpNed/01_Korrespondance ind/01 Bygherre/Emails/.Villa > "up and go".1.N0LkFe failed: Invalid argument > mkstemp 2001_12_Villa_OpNed/01_Korrespondance ind/01 Bygherre/Emails/.nyt > p? tegnefronten?.1.8ZzfZ6 failed: Invalid argument > > If I look for these files on the source filesystem, I find that: > > [samba@fserv SAGER_igangvaerende]# find . -name "Villa*up and go*" > ./2001_12_Villa_OpNed/01_Korrespondance ind/01 > Bygherre/Emails/.AppleDouble/Villa "up and go".1 > ./2001_12_Villa_OpNed/01_Korrespondance ind/01 Bygherre/Emails/Villa "up > and go".1 > > And as I have .AppleDouble in my exclude file (no trailing slash), the > problem appearsThe trailing slash is not necessary to exclude a directory.> to be due to my naive usage of the exclude file. As far as I under stand > now, the > behaviour is due to the .AppleDouble directory not getting created on the > destination, > and due to the lacking slash in the exclude file, rsync still tries to copy > the files within > this directory. The only thing I do not understand now, is the prepended > dot, so eg. Villa > becomes .Villa.To make the temp files a template is created by prepending dot and appending .XXXXXX, the XXXXXX is replaced by simi-random chars by mkstemp or in the absence of mkstemp tempfile. If correctly built on a Linux box rsync will call mkstemp followed by fchmod. The only way you could get a invalid arguments error without .XXXXXX at the end of the file name would be if mkstemp succeeded but with preserve_perms enabled fchmod failed which is nearly impossible in this context. If incorrectly built or on a some non-Linux platforms it does a mktemp followed by do_open which could produce the error condition you present. Based on this i have to conclude that your binary was incorrectly built. I am curious though as to what is causing the problem. It would help tremendously if you could narrow it down to a small test case that strace could be run on. Also, try it to a native filesystem on a reliable interface. In other words ext[23], reiserfs, jfs or xfs on IDE or SCSI; no FAT, USB or firewire. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and Schmitt