Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Jan 2009 23:37:06 +0100
From:      Polytropon <freebsd@edvax.de>
To:        "Andy Wodfer" <wodfer@gmail.com>
Cc:        freebsd-questions <freebsd-questions@freebsd.org>
Subject:   Re: Help! locate.code /tmp: filesystem full
Message-ID:  <20090115233706.0bccadbe.freebsd@edvax.de>
In-Reply-To: <23ed14b80901151237v180b28e9i7cfea923b69aeda1@mail.gmail.com>
References:  <23ed14b80901141034l16ee0dedp9837e4f1162e253b@mail.gmail.com> <23ed14b80901151237v180b28e9i7cfea923b69aeda1@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, 15 Jan 2009 21:37:24 +0100, "Andy Wodfer" <wodfer@gmail.com> 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, ...



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