From owner-freebsd-questions@FreeBSD.ORG Thu Nov 30 14:55:30 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA3AA16A5F6 for ; Thu, 30 Nov 2006 14:55:30 +0000 (UTC) (envelope-from cptsalek@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90BD543E08 for ; Thu, 30 Nov 2006 14:47:47 +0000 (GMT) (envelope-from cptsalek@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so2463772wxc for ; Thu, 30 Nov 2006 06:47:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Gn8ID5CQ30HRiy1JFnd52dgCYymP8QHfq0K1sMjFxRpCaR3a0XyhQOdaKPjofB4bM15hDTBfbO6dvZ9+D8sAeqABCCzWj3lYYlQpOZoyhYpdL5XfYjpO5Vl7mGlrHkwNfC4itCNLHOdyIyMDwTOpmjBfhh3S6lL4mmibCk2cTXI= Received: by 10.70.29.14 with SMTP id c14mr6419720wxc.1164898073324; Thu, 30 Nov 2006 06:47:53 -0800 (PST) Received: by 10.70.14.20 with HTTP; Thu, 30 Nov 2006 06:47:53 -0800 (PST) Message-ID: <14989d6e0611300647q3974e751hd84ac4e67c80cb0c@mail.gmail.com> Date: Thu, 30 Nov 2006 15:47:53 +0100 From: "Christian Walther" To: "Marcelo Maraboli" In-Reply-To: <456EE9E2.7070606@usm.cl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061130112939.12787.qmail@web57808.mail.re3.yahoo.com> <456EE9E2.7070606@usm.cl> Cc: Rachel Florentine , freebsd-questions@freebsd.org Subject: Re: Data Recovery X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2006 14:55:30 -0000 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. ;)