Date: Thu, 30 Nov 2006 15:47:53 +0100 From: "Christian Walther" <cptsalek@gmail.com> To: "Marcelo Maraboli" <marcelo.maraboli@usm.cl> Cc: Rachel Florentine <rachel_florentine@yahoo.com>, freebsd-questions@freebsd.org Subject: Re: Data Recovery Message-ID: <14989d6e0611300647q3974e751hd84ac4e67c80cb0c@mail.gmail.com> In-Reply-To: <456EE9E2.7070606@usm.cl> References: <20061130112939.12787.qmail@web57808.mail.re3.yahoo.com> <456EE9E2.7070606@usm.cl>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't think that rsync can cope with hardlinks. Best way to do a "backup" like this is: tar -clf - / | ( cd /ad2 ; tar -xf - ) The "-l" flag will stay on the specified filesystem. If you forget this option tar (and any other command, even cp and rsync with their respective option) will copy /ad2 into itself, e.g. /ad2/ad2, which might lead to a kind of recursion. BTW: No, there isn't any tool that might recover from a desaster like the one you specified. Either the files you describe as being "fried" have either been overwritten with some other content, or changed in any other way. You need a backup to recover from this. ;)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14989d6e0611300647q3974e751hd84ac4e67c80cb0c>