From owner-freebsd-current@FreeBSD.ORG Tue Feb 5 16:58:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BC2D16A418 for ; Tue, 5 Feb 2008 16:58:05 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 7926113C457 for ; Tue, 5 Feb 2008 16:58:04 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id m15Gvxmk057381; Tue, 5 Feb 2008 19:57:59 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id m15GvxCT057380; Tue, 5 Feb 2008 19:57:59 +0300 (MSK) (envelope-from yar) Date: Tue, 5 Feb 2008 19:57:58 +0300 From: Yar Tikhiy To: Ed Schouten Message-ID: <20080205165758.GC56373@comp.chem.msu.su> References: <20080203121514.GI3539@comp.chem.msu.su> <20080203133019.GL1179@hoeg.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080203133019.GL1179@hoeg.nl> User-Agent: Mutt/1.5.9i Cc: FreeBSD Current Subject: Re: fsck remounts / read-write? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2008 16:58:05 -0000 On Sun, Feb 03, 2008 at 02:30:19PM +0100, Ed Schouten wrote: > * Yar Tikhiy wrote: > > Hi all, > > > > Has anybody else noticed the following strangeness: running fsck > > on the read-only / (from single user) results in the / mount upgraded > > to read-write? E.g.: > > [...] > > > > I guess that `fsck /' issues a mount reload after modifying the FS, > > but IMHO it shouldn't remount the FS read-write, should it? > > Could be related to this PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/106636 Thank you for the pointer to your PR! Then the bug might be related to the new nmount(2) syscall, which is used now by fsck(8) and mountd(8). -- Yar