From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 13 08:32:04 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF82216A415 for ; Fri, 13 Oct 2006 08:32:04 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from leia.fdn.fr (ns0.fdn.org [80.67.169.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5919343D73 for ; Fri, 13 Oct 2006 08:32:00 +0000 (GMT) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by leia.fdn.fr (8.13.3/8.13.3/FDN) with ESMTP id k9D8VwJX015283 for ; Fri, 13 Oct 2006 10:31:59 +0200 Received: by smtp.zeninc.net (smtpd, from userid 1000) id 25B0A3F17; Fri, 13 Oct 2006 10:31:53 +0200 (CEST) Date: Fri, 13 Oct 2006 10:31:53 +0200 From: VANHULLEBUS Yvan To: freebsd-hackers@freebsd.org Message-ID: <20061013083152.GA5885@zen.inc> References: <20061013074136.GA31459@zen.inc> <20061013080407.GA26522@britannica.bec.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061013080407.GA26522@britannica.bec.de> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: Fscking a partition mounted Read only... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 08:32:04 -0000 On Fri, Oct 13, 2006 at 10:04:07AM +0200, Joerg Sonnenberger wrote: > On Fri, Oct 13, 2006 at 09:41:37AM +0200, VANHULLEBUS Yvan wrote: > > > > Later, if root filesystem is remounted readonly, then fsck is called, > > it will says "NO WRITE ACCESS". > > mount -ur / > > or if your fstab is not matching the system configuration > > mount -ur /dev/$ROOT / That's what I tried (using the mount command or the mount syscall). Fsck runs, but starts by "NO WRITE ACCESS", and I don't know what will happen if it detects and try to fix some problems on the filesystem. Yvan. -- NETASQ http://www.netasq.com