From owner-freebsd-questions@FreeBSD.ORG Wed Sep 23 21:20:24 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 6AE8B106566C for ; Wed, 23 Sep 2009 21:20:24 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay1.uni-muenster.de (ZIVM-EXRELAY1.UNI-MUENSTER.DE [128.176.192.14]) by mx1.freebsd.org (Postfix) with ESMTP id E95528FC0C for ; Wed, 23 Sep 2009 21:20:23 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,440,1249250400"; d="scan'208";a="283525097" Received: from zivmaildisp2.uni-muenster.de (HELO ZIVMAILUSER03.UNI-MUENSTER.DE) ([128.176.188.143]) by zivm-relay1.uni-muenster.de with ESMTP; 23 Sep 2009 23:20:22 +0200 Received: by ZIVMAILUSER03.UNI-MUENSTER.DE (Postfix, from userid 149459) id B0C951B0751; Wed, 23 Sep 2009 23:20:22 +0200 (CEST) Date: Wed, 23 Sep 2009 23:20:22 +0200 (CEST) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Polytropon Message-ID: In-Reply-To: <20090923225657.f39b0f19.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: some issues with 9-CURRENT 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: Wed, 23 Sep 2009 21:20:24 -0000 Polytropon schrieb am 2009-09-23: > On Wed, 23 Sep 2009 17:02:24 +0200 (CEST), Alexander Best > wrote: > > however if i do `mount -r -o noatime /dev/label/usr /usr` and run > > `fsck > > /dev/label/usr` fsck isn't able to gain write access. > The fsck program should - as far as I know - only be used on > unmounted (!) file systems. In order to perform fsck with the > ability of file system modifications, umount the file system > and run fsck (maybe with options you desire) again. 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. alex