Article View: aus.computers.linux
Article #1157Re: "lost+found" files?
From: Will Kemp
Date: Mon, 23 Jun 2008 06:51
Date: Mon, 23 Jun 2008 06:51
52 lines
3433 bytes
3433 bytes
Felix Karpfen wrote: > On 2008-06-21, "Robert Swan" swan.r.l@gmail.com <"Robert Swan"> wrote: > >> Can be a challenge finding where these things are documented, but >> "file" is often helpful when trying to work out what a file is. >> >> And it's not good to be finding things in lost+found. That indicates >> some level of file system corruption > > Alas - that was indeed the case. > > I had a major crash. And my file system was corrupted very badly. > It is still unclear why it happened; but all is fixed now (apart > from the files in "lost+found") and I refrain from spelling out the > details. However, I would have been history, if I had not had a backup > fully-operational (Linux) system on my box from which to repair the > corrupted disk partition. Was it an ext3 file system? > Thank you for the advice and the pointer to the "file" command. The > output of the "file" command reads: > > [felixk@ ~]$ file 75584621 > 75584621: ERROR: cannot open `75584621' (No such file or directory) > > - which is probably just another indication that I was in big trouble! Maybe, maybe not. Anything that gets moved to Lost+Found is likely to be only part of a file that's become disembodied from the rest of it and the original directory entry. So depending on what the original file was, it's sometimes possible to recover useful data. Although, that's really only likely to be useful if it's a text file or a sound file or some format where one part on its own could make sense. Part of a book could still save a lot of writing, and part of a recorded interview could be useful. Part of a photo or part of an executable is probably going to be totally useless! Have you tried opening them with a text editor? > I assume thaat I can safely delete the entries in "lost+found" since > everything works again and none of the entries appear to be missed. If you can't open them with a text editor they're probably not going to be any use anyway. But it might not do any harm to hang onto them for a while, as sometimes you don't realise something missing for ages. -- http://SnapAndScribble.com
Technical Details
Message-ID:
<kJH7k.69671$312.69354@newsfe12.ams2>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news4.google.com!feeder.news-service.com!border1.nntp.ams.giganews.com!nntp.giganews.com!ramfeed1.eweka.nl!eweka.nl!hq-usenetpeers.eweka.nl!69.16.177.246.MISMATCH!cyclone03.ams!news.ams.newshosting.com!npeersf01.ams!newsfe12.ams2.POSTED!53ab2750!not-for-mailReferences:
<slrng5k08e.4ah.felixk@carrot.cabbage.patch> <hmbui5-8qh.ln1@rswan.netspace.net.au> <slrng5r5kl.5uv.felixk@carrot.cabbage.patch>Show Full Headers
Complete Article Headers
X-Google-Thread: 102983,abf261a6654f7811 X-Google-Attributes: gid102983,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news4.google.com!feeder.news-service.com!border1.nntp.ams.giganews.com!nntp.giganews.com!ramfeed1.eweka.nl!eweka.nl!hq-usenetpeers.eweka.nl!69.16.177.246.MISMATCH!cyclone03.ams!news.ams.newshosting.com!npeersf01.ams!newsfe12.ams2.POSTED!53ab2750!not-for-mail From: Will Kemp <will@xxxx.swaggie.net> User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 Newsgroups: aus.computers.linux Subject: Re: "lost+found" files? References: <slrng5k08e.4ah.felixk@carrot.cabbage.patch> <hmbui5-8qh.ln1@rswan.netspace.net.au> <slrng5r5kl.5uv.felixk@carrot.cabbage.patch> In-Reply-To: <slrng5r5kl.5uv.felixk@carrot.cabbage.patch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Lines: 52 Message-ID: <kJH7k.69671$312.69354@newsfe12.ams2> NNTP-Posting-Host: 86.27.60.149 X-Complaints-To: http://netreport.virginmedia.com X-Trace: newsfe12.ams2 1214203856 86.27.60.149 (Mon, 23 Jun 2008 02:50:56 EDT) NNTP-Posting-Date: Mon, 23 Jun 2008 02:50:56 EDT Organization: virginmedia.com Date: Mon, 23 Jun 2008 07:51:00 +0100