From owner-freebsd-hackers Mon Aug 23 10:23:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E923015016; Mon, 23 Aug 1999 10:22:47 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA69902; Mon, 23 Aug 1999 11:21:56 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA39962; Mon, 23 Aug 1999 11:22:35 -0600 (MDT) Message-Id: <199908231722.LAA39962@harmony.village.org> To: Poul-Henning Kamp Subject: Re: Mandatory locking? Cc: Greg Lehey , Matthew Dillon , FreeBSD Hackers , FreeBSD Committers , Garrett Wollman In-reply-to: Your message of "Mon, 23 Aug 1999 09:47:40 +0200." <7569.935394460@critter.freebsd.dk> References: <7569.935394460@critter.freebsd.dk> Date: Mon, 23 Aug 1999 11:22:35 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I did a remote geographic disk based mirroring product a few years ago, I just had an ioctl that said that this disk was special for a while. Then the open routine would fail. This flag was cleared in the close routine (and by the companion ioctl). I did allow users to open the device w/o read and write to get status on the device, but that was it until the rebuilding process was complete. Granted, this was the control device for the mirroring driver... But that worked fairly well. I only needed to do this in recovery situations for a few hundred disk I/Os, so the average user would likely have never noticed. Oh, this was on Solaris, but the concepts are exactly the same for FreeBSD. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message