Date: Fri, 13 Oct 2006 14:16:51 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-hackers@freebsd.org, rick-freebsd@kiwi-computer.com Subject: Re: Fscking a partition mounted Read only... Message-ID: <200610131416.51379.jhb@freebsd.org> In-Reply-To: <20061013174215.GB83555@keira.kiwi-computer.com> References: <20061013074136.GA31459@zen.inc> <20061013080407.GA26522@britannica.bec.de> <20061013174215.GB83555@keira.kiwi-computer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 13 October 2006 13:42, Rick C. Petty wrote: > 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 / > > I'm pretty sure that's what he tried (hence "remounted readonly"). I've > noticed this behavior as well and it is quite frustrating. If you boot > single-user, / will be mounted read-only and you can fsck it. If you do: > > mount -u / > mount -u -r / > > You can no longer fsck it. I've been meaning to track this down and/or > file a PR. I'm pretty sure this used to work just fine in 3.x and 5.x. I think it's broken in 5.x as well. It's fallout from GEOM IIRC, and it is annoying. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610131416.51379.jhb>