Date: Tue, 18 Apr 1995 20:06:19 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: fenner@parc.xerox.com (Bill Fenner) Cc: freebsd-current@FreeBSD.org Subject: Re: fsck trashes / if no /lost+found? Message-ID: <199504181806.UAA04362@uriah.heep.sax.de> In-Reply-To: <95Apr17.194031pdt.49864@crevenia.parc.xerox.com> from "Bill Fenner" at Apr 17, 95 07:40:28 pm
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)? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504181806.UAA04362>