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 [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Mandatory locking? Daniel C. Sobral
- Re: Mandatory locking? Terry Lambert
- Re: Mandatory locking? Andrew Reilly
- Locking in Vinum (was: Mandato... Greg Lehey
- Re: Locking in Vinum (was: Man... Terry Lambert
- Re: Locking in Vinum (was: Man... Greg Lehey
- Re: Locking in Vinum (was: Man... Terry Lambert
- Re: Locking in Vinum (was: Man... Sean Eric Fagan
- Re: Locking in Vinum (was: Man... Wes Peters
- Re: Locking in Vinum (was: Man... Greg Lehey
- Re: Mandatory locking? Warner Losh
- Re: Mandatory locking? Garance A Drosihn
- Re: Mandatory locking? Greg Lehey
- Re: Mandatory locking? Tim Vanderhoek
- Re: Mandatory locking? Mark Murray
- Re: Mandatory locking? Garance A Drosihn
- Re: Mandatory locking? Tim Vanderhoek
- Re: Mandatory locking? Wes Peters
- Re: Mandatory locking? Tim Vanderhoek
- Re: Mandatory locking? Tim Vanderhoek
- Re: Mandatory locking? Greg Lehey