From owner-cvs-all  Mon Mar 11  5:53:12 2002
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5F42A37B400; Mon, 11 Mar 2002 05:53:00 -0800 (PST)
Received: (from phk@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g2BDr0891090;
	Mon, 11 Mar 2002 05:53:00 -0800 (PST)
	(envelope-from phk)
Message-Id: <200203111353.g2BDr0891090@freefall.freebsd.org>
From: Poul-Henning Kamp <phk@FreeBSD.org>
Date: Mon, 11 Mar 2002 05:53:00 -0800 (PST)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/ufs/ffs ffs_vfsops.c
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

phk         2002/03/11 05:53:00 PST

  Modified files:
    sys/ufs/ffs          ffs_vfsops.c 
  Log:
  As a XXX bandaid open the mounted device READ/WRITE even if we only mount
  read-only.
  
  The trouble here is that we don't reopen the device in read/write mode
  when we remount in read/write mode resulting in a filesystem sending
  write requests to a device which was only opened read/only.
  
  I'm not quite sure how such a reopen would best be done and defer
  the problem to more agile hackers.
  
  Revision  Changes    Path
  1.169     +14 -0     src/sys/ufs/ffs/ffs_vfsops.c

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message