From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 16:37:25 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CFA816A4CE for ; Sun, 27 Feb 2005 16:37:25 +0000 (GMT) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DBED43D64 for ; Sun, 27 Feb 2005 16:37:01 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id j1RGabqS003092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Feb 2005 08:36:38 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id j1RGaaTC003090; Sun, 27 Feb 2005 08:36:36 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Sun, 27 Feb 2005 08:36:36 -0800 From: "Loren M. Lang" To: Thomas Foster Message-ID: <20050227163636.GA1672@alzatex.com> References: <00f201c515fa$8caef250$4300a8c0@home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00f201c515fa$8caef250$4300a8c0@home.lan> User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C cc: freebsd-fs@freebsd.org Subject: Re: UFS2 Recovery Questions X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 16:37:25 -0000 On Fri, Feb 18, 2005 at 12:43:45PM -0800, Thomas Foster wrote: > Please excuse me if this is not the correct forum in which to ask this question and please try to bear with me. I was hoping to understand a few things about attempting to retrieve information from a drive on my FreeBSD 5.3 system. > > I recently was rearranging my web server content and accidentally removed a symbolic link recursively > > root@host # rm -rf music Are you sure the command wasn't rm -fr music/? The final / can make a big differnece with symlinks. It forces the system to look it up as a directory first, and without that, I think it would only remove the symlink. Also, -r should never be needed for a symlink, even if it point to a directory. > > The music link pointed to a directory that existed on a spserate drive mounted as /storage > > music -> /storage/Music/Mp3s > > > Now the questions is.. are the files even recoverable? Is this a lost cause? Any additional information required, any comments or suggestions, anything would be helpful. I thank you for your time in the matter. > > Thomas Foster > http://www.section6.net > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C