>I have a minor point related to your efforts, not multipath itself: >What happens if another task (or machine) looks at that volume when it >has your bogus volid?
Hi John, First off ... I think that multipath should be handled below the gendisk layer and it shouldn't be my problem at all. In the meantime I am trying to prevent confusion in our volume management code by recognizing multipath devices on 390 in the method I described. Threading issues - none - whomever opens the engine (user mode config tool) is guaranteed exclusive access. Shared device issues - we are adding clustering support this year and the distributed lock manager should protect me. But let me reiterate - I don't see the benefit of allowing multipath devices to surface past the gendisk layer. Um ... I think I answered your question. The approach seems Ok to me ... just inadequte ... I think more work needs to be done to support multipath devices. -Don
