Date: Fri, 13 Oct 2006 13:57:58 -0500 From: "Rick C. Petty" <rick-freebsd@kiwi-computer.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Fscking a partition mounted Read only... Message-ID: <20061013185757.GA88689@keira.kiwi-computer.com> In-Reply-To: <200610131416.51379.jhb@freebsd.org> References: <20061013074136.GA31459@zen.inc> <20061013080407.GA26522@britannica.bec.de> <20061013174215.GB83555@keira.kiwi-computer.com> <200610131416.51379.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 13, 2006 at 02:16:51PM -0400, John Baldwin wrote: > On Friday 13 October 2006 13:42, Rick C. Petty wrote: > > > > 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. Grr, I meant 4.x not 5.x, and I thought the problem started about the time bg fsck was introduced... -- Rick C. Petty
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061013185757.GA88689>