On Thu, 15 Jun 2000, Kurt Garloff wrote:
>No. And it would be cleared by the exception handling as sooner or later you
>would get a SCSI reset because of the reservation conflicts ...
While linux certainly would go down this path. NO SCSI HOST/BUS/DEVICE
SHOULD !_EVER_! BE RESET DUE TO A RESERVATION CONFLICT. The fact that
linux will see a reservation conflict as a reset canidate error is just
#^#%% wrong. Obviously someone either failed to read an entire section
of the SCSI-2 spec or is just too lazy to care about proper operations.
>> Or is this handled via some other mechanism?
>> + Driver(s) responsible for handling any+all multi-initiator issues.
>> + LVM, clustering, or somesuch?
>
>No.
>Of course, you can design software to handle this ...
There is no page cache sync between machines. Thus, who ever flushes their
change(s) to disk last wins. You'd need something like nfsd to handle
buffer sync -- and all writes would have to be sync or the problem gets
alot more complicated. [And yes, I've thought about this sort of thing
a great deal over the past few years.]
--Ricky
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
