On 11/1/06, Phil Smith III <[EMAIL PROTECTED]> wrote:
To add to what others have said, don't forget the QUERY MDISK command -- if LINUX123 has a problem with its 400 disk, QUERY MDISK USER LINUX123 400 DIR LOCATION will tell him more than he wants to know about the disk.
And don't forget that it is way easier if you know that each Linux server needs to IPL from its 200 disk and has swap space at 210-21F, that disks in 3xx range are used in LVM, etc. I find that some large shops now do similar tricks in the IOCP for their LPARs (like the console address is the same in each LPAR so you can move images around without the need to change things inside). Back in the old days when HDA's were swapped at will, you'd be asking for real trouble if you coded a dependency on the hardware address. But even in these days, a storage administrator will want the ability to move a virtual machine's data without having to make changes inside that server (like for spreading the data over different loops in the storage subsystem). A scheme where the virtual and real address match "most of the time" is probably even more tricky than when there is no such relation. Rob ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
