Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Jan 2009 02:24:21 +0100
From:      Polytropon <freebsd@edvax.de>
To:        Mel <fbsd.questions@rachie.is-a-geek.net>
Cc:        freebsd-questions@freebsd.org, Andy Wodfer <wodfer@gmail.com>
Subject:   Re: Help! locate.code /tmp: filesystem full
Message-ID:  <20090123022421.d555261e.freebsd@edvax.de>
In-Reply-To: <200901221024.39978.fbsd.questions@rachie.is-a-geek.net>
References:  <23ed14b80901141034l16ee0dedp9837e4f1162e253b@mail.gmail.com> <23ed14b80901151237v180b28e9i7cfea923b69aeda1@mail.gmail.com> <20090115233706.0bccadbe.freebsd@edvax.de> <200901221024.39978.fbsd.questions@rachie.is-a-geek.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, 22 Jan 2009 10:24:39 -0900, Mel <fbsd.questions@rachie.is-a-geek.net> wrote:
> In short: reboot in single user mode, then run fsck -y at the prompt.
> 
> Never ever run fsck -y on a live filesystem.

A very good hint. Didn't I mention it? No? Bad idea.

Background concept: The fsck utility does changes to the file system
when repairing it, and the kind of these changes implies that the file
system is not mounted, so there's no unexpected interruption by maybe
a write operation from a program.

That's what downtime is good for - letting fsck doing its job well.




-- 
Polytropon
>From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20090123022421.d555261e.freebsd>