Richard Siemers wrote:
To bad it won't let you add a 2nd export on the same LUN# to the one host, then un-export it from the hostset... with the net result of just one host losing access to the lun, kind of like how switches resolve multiple zones that have the same members.
I think you can get that ... kind of ...
If you were to export the volume to an individual host as a different Host LUN ID, then do a storage discovery, the hosts multipathing software might treat the extra LUN ID as another path to the same volume. Then you unexport the volume from the host set .. hosts with the volume individually mapped will see path failures
I've only tried this once, was for HP-UX I think.