Date: Tue, 18 Apr 1995 11:24:44 -0700 From: David Greenman <davidg@Root.COM> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: fenner@parc.xerox.com (Bill Fenner), freebsd-current@FreeBSD.org Subject: Re: fsck trashes / if no /lost+found? Message-ID: <199504181824.LAA01700@corbin.Root.COM> In-Reply-To: Your message of "Tue, 18 Apr 95 20:06:19 %2B0200." <199504181806.UAA04362@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>As Bill Fenner wrote: >> >> I am running SNAP-950322. I crashed hard, and on the way up, fsck tried to >> reconnect a file when fsck'ing /usr. Apparently, for some reason there was >> no /usr/lost+found, and fsck printed an error something like "no room in /" >> when it said it was trying to create it. The fsck failed, and when I fsck'd >> manually it said there was no /, and it ended up reconnecting all the >> directories in /lost+found (after creating /lost+found). > >Terry tells about this every second day. :-) > >Time to add the appropriate part to newfs(8)? I asked Kirk about this and he said "no". I might still have the email around somewhere. -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504181824.LAA01700>