I am using rsync to synchronize directories and have noticed (I think) the following behavior.....
I created a snapshot on my filer and ran rsync from the snapshot directory to copy the files to a remote directory. The following day I mistakenly ran rsync from the same snapshot directory without taking a new snapshot.
On almost all directories rsynced in this fashion there were no differences between the source and destination directories, as expected. However, in one directory rsync deleted the directory ".nfs18C041/" and all files and subdirectories of this directory from the destination file system, indicating that it had disappeared from the snapshot directory. A check of the two directories using find that was run between the execution of the two rsync commands showed that this directory was the only difference between the two directories other than symbolic link dates and directory sizes which we expected.
Given the nature of the .nfs directory it occurs to me that removing this type of directory from snapshots when they disappear from the regular file system might be intentional.
Does this seem reasonable or have I done something dumb and possibly misinterpreted what occurred? That couldn't be, could it?
Thanks.
Greg Kitch UCLA SEASnet Computing Facility
Does this seem reasonable or have I done something dumb and possibly misinterpreted what occurred? That couldn't be, could it?
Wouldn't the more likely answer be that the .nfs directory was never in the snapshot, and was rather created in Copy #1 via something that happened there afterwards (perhaps even as part of the rsync process), and that didn't happen in Copy #2?
Bruce
Thanks Bruce, and of course you're right. That is what I realized about one hour after I posted the message and thought more carefully about it.
I knew I felt kind of dumb when I sent the message and it will teach me to take a bit more time to think something over before I post a question.
Greg
Does this seem reasonable or have I done something dumb and possibly misinterpreted what occurred? That couldn't be, could it?
Wouldn't the more likely answer be that the .nfs directory was never in the snapshot, and was rather created in Copy #1 via something that happened there afterwards (perhaps even as part of the rsync process), and that didn't happen in Copy #2?
Bruce
----- Original Message ----- From: Greg Kitch kitch@seas.ucla.edu To: Bruce Sterling Woodcock sirbruce@ix.netcom.com Cc: toasters@mathworks.com Sent: Sunday, February 06, 2000 8:10 PM Subject: Re: snapshot behavior
Thanks Bruce, and of course you're right. That is what I realized about one hour after I posted the message and thought more carefully about it.
I knew I felt kind of dumb when I sent the message and it will teach me to take a bit more time to think something over before I post a question.
Aww, now you make me feel guilty. :)
Sometimes we all miss the obvious. (I've preached here about such things before. The #1 thing I had to learn as an admin is to discipline myself to look for the obvious things first, and not waste a lot of time thinking the problem must be really arcane and complex when it is just a matter of a typo or a misplaced parameter. And I've still been guilty of it myself more times than I can count. How many times have you been just *positive* an IP address or netmask was correct, and it wasn't?)
Bruce
Sometimes we all miss the obvious. (I've preached here about such things before. The #1 thing I had to learn as an admin is to discipline myself to look for the obvious things first, and not waste a lot of time thinking the problem must be really arcane and complex when it is just a matter of a typo or a misplaced parameter.
Unless it involves Windows - then it IS usualy the more arcane or obscure and unrelated thing rather then the ovbious - or at least in my experience ;p
----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO