From owner-freebsd-questions@FreeBSD.ORG Thu Jan 15 22:37:17 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9819106564A for ; Thu, 15 Jan 2009 22:37:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id 97C838FC21 for ; Thu, 15 Jan 2009 22:37:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r55.edvax.de (port-92-196-14-53.dynamic.qsc.de [92.196.14.53]) by mx01.qsc.de (Postfix) with ESMTP id 2F55C3CF69; Thu, 15 Jan 2009 23:37:12 +0100 (CET) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id n0FMb6uW001689; Thu, 15 Jan 2009 23:37:06 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Thu, 15 Jan 2009 23:37:06 +0100 From: Polytropon To: "Andy Wodfer" Message-Id: <20090115233706.0bccadbe.freebsd@edvax.de> In-Reply-To: <23ed14b80901151237v180b28e9i7cfea923b69aeda1@mail.gmail.com> References: <23ed14b80901141034l16ee0dedp9837e4f1162e253b@mail.gmail.com> <23ed14b80901151237v180b28e9i7cfea923b69aeda1@mail.gmail.com> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions Subject: Re: Help! locate.code /tmp: filesystem full X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 22:37:18 -0000 On Thu, 15 Jan 2009 21:37:24 +0100, "Andy Wodfer" wrote: > Should I run fsck -y? Is it safe to do so? At least, fsck will do its best to repair the defective file system. As you have seen from the messages, you will surely lose some files when their information gets cleared. If you use -y, fsck is allowed to do anything it considers neccessary doing. You could use fsck in preen mode (-p) to have less defects corrected. If it's possible, try to backup all important data. If fsck deletes something, you could restore it afterwards. Your goal should be to get your file system into a consistent state again. Worse kinds of data loss can follow. It hurts, I know it... :-( -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...