Fix some typos..... #########################################################################################################
In fact, there is no problem for MPxIO name in technology. It only matters for storage admins to remember the name. I think there is no way to give short aliases to these long tedious MPxIO name. And I just have only one HBA card, so I don't need multipath indeed. The simple name -- cxtxdx will be much more easier. Furthermore, my ultimate goal is to map the disk in MPxIO path to the actual physical slot position. And If there is a broken HDD, I can easily know to replace which one. BTW, the "luxadm led_blink" may not work in the commodity hardware and only works in Sun's proprietary disk array. I think it is a common situation for storage admins. **How do you replace the broken HDDs in your best practice?** Thanks. Fred -----Original Message----- From: James C. McPherson [mailto:j...@opensolaris.org] Sent: 星期三, 六月 02, 2010 10:27 To: Fred Liu Cc: zfs-discuss@opensolaris.org Subject: Re: [zfs-discuss] Is it possible to disable MPxIO during OpenSolaris installation? On 2/06/10 12:01 PM, Fred Liu wrote: > Yes. But the output of zpool commands still uses MPxIO naming convention > and format command cannot find any disks. _But_ ? What is the problem with ZFS using the device naming system that the system provides it with? Do you mean that you cannot see any plain old targets, or that no disk devices of any sort show up in your host when you are installing? What is your actual problem, and why do you think that turning off MPxIO will solve it? James C. McPherson -- Senior Software Engineer, Solaris Oracle http://www.jmcp.homeunix.com/blog _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
