Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Sep 2009 00:14:39 +0200
From:      Polytropon <freebsd@edvax.de>
To:        Alexander Best <alexbestms@math.uni-muenster.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: some issues with 9-CURRENT
Message-ID:  <20090924001439.79e053c1.freebsd@edvax.de>
In-Reply-To: <permail-200909232120221e86ffa8000059c8-a_best01@message-id.uni-muenster.de>
References:  <20090923225657.f39b0f19.freebsd@edvax.de> <permail-200909232120221e86ffa8000059c8-a_best01@message-id.uni-muenster.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Wed, 23 Sep 2009 23:20:22 +0200 (CEST), Alexander Best <alexbestms@math.uni-muenster.de> wrote:
> thx. i thought since / gets mounted read-only and fsck is able to check it
> with write access this would apply to read-only mountpoints in general.

Because fsck resides in /sbin, it is required - in SUM - that /
is mounted and accessible for program execution. The best solution
is to mount it ro (-r) to get minimal "interference", but generally,
only unmounted partitions should be fscked. The / partition is an
excelion due to a neccessary evil. :-)

(If you're running fsck from a live system CD, you usually don't
mount anything. Running fsck on rw-mounted partitions can cause
damage to the file systems and should be avoided.)



-- 
Polytropon
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?20090924001439.79e053c1.freebsd>