From owner-freebsd-questions@FreeBSD.ORG Thu Jan 22 19:24:41 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 4E63C106564A for ; Thu, 22 Jan 2009 19:24:41 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 1E6A08FC13 for ; Thu, 22 Jan 2009 19:24:40 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 4AD86AFC1FF; Thu, 22 Jan 2009 10:24:40 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org, Polytropon Date: Thu, 22 Jan 2009 10:24:39 -0900 User-Agent: KMail/1.9.10 References: <23ed14b80901141034l16ee0dedp9837e4f1162e253b@mail.gmail.com> <23ed14b80901151237v180b28e9i7cfea923b69aeda1@mail.gmail.com> <20090115233706.0bccadbe.freebsd@edvax.de> In-Reply-To: <20090115233706.0bccadbe.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901221024.39978.fbsd.questions@rachie.is-a-geek.net> Cc: Andy Wodfer Subject: Re: Help! locate.code /tmp: filesystem full X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 19:24:41 -0000 On Thursday 15 January 2009 13:37:06 Polytropon wrote: > On Thu, 15 Jan 2009 21:37:24 +0100, "Andy Wodfer" wrote: Added context: > > Here's the output of fsck (this was a new command to me): > > > > # fsck > > ** /dev/ar0s1a (NO WRITE) > > 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. fsck on a live filesystem (hint: NO WRITE) is a bad idea. Doing an fsck that is supposed to repair stuff, always requires downtime, unless you use background_fsck. However, many people discourage it's usage as it can leave some errors unfixed. In short: reboot in single user mode, then run fsck -y at the prompt. Never ever run fsck -y on a live filesystem. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.