From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 19:40:57 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 CF20016A4CE for ; Wed, 2 Mar 2005 19:40:57 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4843643D2F for ; Wed, 2 Mar 2005 19:40:55 +0000 (GMT) (envelope-from tbonius@comcast.net) Received: from ostros (c-24-18-102-54.client.comcast.net[24.18.102.54]) by comcast.net (sccrmhc12) with SMTP id <2005030219405401200run17e>; Wed, 2 Mar 2005 19:40:54 +0000 Message-ID: <001801c51f5f$cdde9dc0$4300a8c0@home.lan> From: "Thomas Foster" To: "Loren M. Lang" References: <00f201c515fa$8caef250$4300a8c0@home.lan> <20050227163636.GA1672@alzatex.com> Date: Wed, 2 Mar 2005 11:41:17 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 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: Wed, 02 Mar 2005 19:40:57 -0000 Yes, I did use the -r option (bad muscle memmory habits), and it removed the symlink and the directories it pointed at. At this point I am still attempting to rescue the data from an image via sleuthkit T ----- Original Message ----- From: "Loren M. Lang" To: "Thomas Foster" Cc: Sent: Sunday, February 27, 2005 8:36 AM Subject: Re: UFS2 Recovery Questions > 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 > >