[SunHELP] filesystem question

[Fletcher, Joe]

It describes the contents of "lost+found" as being recovered data that may
potentially be of use to you. Analysis of the contents of the directory may
lead you to recover stuff that otherwise might be lost. It must be said
though that most of the time the recovered stuff is useless wihtout a large
amount of work being done on it. It's usually fragments at best.

-----Original Message-----
From: Edward Chase [mailto:echase at postoffice.providence.edu]
Sent: 2 May 2001 18:55
To: sunhelp at sunhelp.org
Subject: RE: [SunHELP] filesystem question


I'm sorry, but I don't see how this reply adds anything or helps me out???


At 01:15 PM 5/2/2001 -0400, Foust, Kal E wrote:
>I don't know if things have changed regarding filesystems to the point that
>these entries are no longer relevant.  My understanding is that
"lost+found"
>'directories' are created automatically when you build the filesystem.
They
>are used by <fsck> in emergencies and so should not be deleted without
>diligence.  There purpose being that if <fsck> finds a file whose parent
>directory is unknown, it puts the file into the "lost+found" directory at
>the top level of the filesystem.
>
>
>-----Original Message-----
>From: Edward Chase [mailto:echase at postoffice.providence.edu]
>Sent: Wednesday, May 02, 2001 9:47 AM
>To: sunhelp at sunhelp.org
>Subject: Re: [SunHELP] filesystem question
>
>
>It certainly doesn't appear to be...
>
>The first character when doing an "ls" is a "d", not an "l".
>
>
>
>At 08:27 AM 5/2/2001 +0100, Will Mc Donald wrote:
> >Is #028482 a symlink? I have no idea what it is or why it's there but if
it
> >is a symlink you're *probably* safe to delete it.
> >
> >----- Original Message -----
> >From: "Edward Chase" <echase at postoffice.providence.edu>
> >To: <sunhelp at sunhelp.org>
> >Sent: Tuesday, May 01, 2001 9:09 PM
> >Subject: [SunHELP] filesystem question
> >
> >
> > > I was just nosing around a machine and found the following...
> > >
> > > If I "cd /opt/lost+found"
> > > I see a directory "#028482"
> > > If I "cd #028482", I end up at "/"
> > >
> > > I've unmounted the /opt filesystem and fsck'd it.  There are currently
>no
> > > errors.
> > >
> > > What's happening here?
> > > Can I "cd /opt/lost+found" and "rmdir #028482" safely?
> > > If "rmdir" doesn't work, should I "rm -rf #028482"?
> > >
> > > Thanks.
> > >
> > > Solaris 2.5.1, if it's of any importance...

---------------------------------------------------------------
  Edward F. Chase III     |   echase at providence.edu
  Providence College      |   http://www.providence.edu
  Computer Services       |   http://studentweb.providence.edu
  Providence, RI  02918   |

_______________________________________________
SunHELP maillist  -  SunHELP at sunhelp.org
http://www.sunhelp.org/mailman/listinfo/sunhelp


MetaPack
The Lightwell 
12/16 Laystall Street 
Clerkenwell 
London EC1R 4PF 
Tel: +44 (0) 20 7843 6720 
Fax: +44 (0) 20 7843 6721
--------------------------------------------------------------------------
This email is confidential and proprietary; 
all information contained in it must be used only by the addressee in
accordance with MetaPack's terms of business and non-disclosure agreement. 
Disclosure, copying, and distribution to, or use by, anyone other than the
intended recipient is strictly prohibited and may be unlawful.