Date: Sun, 8 Dec 2002 16:27:25 -0800 (PST) From: Archie Cobbs <archie@dellroad.org> To: Julian Elischer <julian@elischer.org> Cc: Archie Cobbs <archie@dellroad.org>, Bruce Evans <bde@zeta.org.au>, Kirk McKusick <mckusick@beastie.mckusick.com>, freebsd-current@FreeBSD.ORG, Thomas-Henning von Kamptz <tomsoft@FreeBSD.ORG> Subject: Re: backgroud fsck is still locking up system (fwd) Message-ID: <200212090027.gB90RQpM075979@arch20m.dellroad.org> In-Reply-To: <Pine.BSF.4.21.0212071255590.55545-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > > Well, I suspected that it might not work... but I would disagree that it > > was *obvious* that it would not work. This was before "mount" had been > > run, so / was supposedly mounted (?) read-only. > > I've seen ufs write back the superblock on unmounting a read-only > filesystem (!). it was a few years ago but I wouldn;t be surprised if it > was still true.. > > After you did it on the filesystem. (ran growfs) what did you do next? > the safe answer would be to pull the plug. "reboot" It seems counter-intuitive that a filesystem mounted "read only" would be modified by the kernel. I'm sure there's some subtlety I'm not aware of though.. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212090027.gB90RQpM075979>