> mount. But if Library Client's tape paths are in error, and his path > definition for DRIVE1 is actually pointing to the logical device for > DRIVE2, and DRIVE2 is already in use by somebody else, he will get an > error trying to open DRIVE2, and that will cause a Reservation Conflict. > > So it would be worth checking to make sure that all the paths on the > LIbrary Clients point to the correct paths.
Also, make sure the s/n and wwn of the drive (q drive f=d) is correct for the rmt/paths you define. . . . but . . . The couple times we had this kind of problem I crawled through all the info for drives, paths, rmt. Everything was correct for all tsm servers and storage agents. But we still got mount failures and reservation conflicts. That's why I finally deleted _everything_ and recreated it all. Do you have dyntrk set on for the fscsi protocol device (lsattr -El fscsiX)? We do. I've often wondered how it interacts with sandiscovery. Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
