Date: Thu, 21 Mar 96 21:38 WET From: uhclem@nemesis.lonestar.org (Frank Durda IV) To: current@freebsd.org Subject: Re: lost+found Message-ID: <m0tzxgp-000CzFC@nemesis.lonestar.org>
next in thread | raw e-mail | index | archive | help
[0] I created most of my filesystems in 2.1.0R with the standard [0]sysinstall newfs, but none of them have lost+found directories. [0]After newfs'ing new drive partitions and such under -current, [0]I've noticed none of them have lost+found directories either. [0]What do I need to do? [1]Nothing, fsck creates them as it needs them. That's what I thought until a recent crash and fsck was unable to create lost+found or did not try. The end result was that I had to get a DOS disk block zapper and rename "tmp" to "lost+found" so that fsck would be happy and quit deleting entire directories at great speed. The failure seemed to spring up when you had an unreferenced directory rather than an unreferenced file. It seems like it remembers to make lost+found when recovering an unreferenced file. Perhaps there were more serious problems with the file system in my case. Now I routinely create lost+found and lost-found so that I can easily make one out of the other in case lost+found gets nuked by the crash. And yes, this all happened on 2.1.0. Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" |"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0tzxgp-000CzFC>