Date: Tue, 30 Aug 2005 09:37:23 +0200 (CEST) From: Svein Halvor Halvorsen <svein-freebsd-questions@theloosingend.net> To: Norberto Meijome <freebsd@meijome.net> Cc: questions@freebsd.org Subject: Re: rsync and moving files [Re: backup w/ snapshots] Message-ID: <20050830093218.B13913@maren.thelosingend.net> In-Reply-To: <43133459.9030000@meijome.net> References: <20050828234043.H22315@maren.thelosingend.net> <20050829161506.E2522@maren.thelosingend.net> <43131C85.1070100@meijome.net> <20050829170053.M3014@maren.thelosingend.net> <43133459.9030000@meijome.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Norberto Meijome [2005-08-30 02:14 +1000] > I take your word wrt to how it works. Assuming of course that you move > within the same filesystem. Yes, I'm talking about the same filsystem. > (touche). yup, that's what would happen....but tha's the nature of the beast > :) don't keep too many snapshots ? ;) > > it'd be great if you could keep a log of all local-mv operations,and then > replay them remotely via ssh. Yes, I thought about that myself. Only I thought I'd keep a list of filename/inode pairs from each sync, so before I do a sync I could compare the lists to find out which files appears to be the same, only with a new name. Then rename those files remotely. In cases where a inode-match does not represent a relink, but just plain inode recycling, so what? Rsync will make the new file up to date.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050830093218.B13913>