From owner-freebsd-hackers Tue Apr 16 7:49:43 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [192.80.55.70]) by hub.freebsd.org (Postfix) with ESMTP id 91F7037B41F for ; Tue, 16 Apr 2002 07:49:35 -0700 (PDT) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id g3CH56x26723 for ; Fri, 12 Apr 2002 13:05:06 -0400 (EDT) Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id g3CH54u18752 for ; Fri, 12 Apr 2002 13:05:05 -0400 (EDT) Received: from dhcp-48-37.mitre.org (128.29.48.37) by mailhub1.mitre.org with SMTP id 9847149; Fri, 12 Apr 2002 13:03:59 -0400 Message-ID: <3CB713CB.629E4AC8@mitre.org> Date: Fri, 12 Apr 2002 13:05:15 -0400 From: "PSI, Mike Smith" Organization: The MITRE Corporation X-Mailer: Mozilla 4.76 [en]C-20010313M (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: mount -u strangeness Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey all, Made a mistake and ran across what may be a bug in mount but am not sure. Now this happened on FreeBSD 3.2 (no comments please, I've already given the powers that be plenty of comments about this). Our password files became corrupted so we entered single user mode to try to repair the situation. But alas, the filesystem booted to read only (not the problem). To be able to access the necessary files, we did a fsck -p mount -u / It worked! The filesystem was now read/write. But the problem was, we intended to do "mount -u -w /". Should "mount -u /" result in a read/write filesystem from a mounted read only? Would this happen if you tried to change any other attribute with -u? It may be the correct operation, but if it isn't, having a filesystem change unknowingly (unintentionally) from read only to read/write could be a bit dangerous I would think. Any thoughts, remembering that this is 3.2 and thus may be ancient history. (not THE) Mike Smith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message