mdump doesn't produce any "human readable" disk ids, only
guids which then have to be correlated via a "zdb -c"
Sean
>Date: Tue, 17 Nov 2009 16:18:52 -0700
>From: Cindy Swearingen
>Subject: Re: [zfs-discuss] building zpools on device aliases
>To: se
sean walmsley wrote:
We have a number of Sun J4200 SAS JBOD arrays which we have multipathed using Sun's MPxIO
facility. While this is great for reliability, it results in the /dev/dsk device IDs
changing from cXtYd0 to something virtually unreadable like
"c4t5000C5000B21AC63d0s3".
Since the
Hi Sean,
I sympathize with your intentions but providing pseudo-names for these
disks might cause more confusion than actual help.
The "c4t5..." name isn't so bad. I've seen worse. :-)
Here are the issues with using the aliases:
- If a device fails on a J4200, a LED will indicate which disk ha
We have a number of Sun J4200 SAS JBOD arrays which we have multipathed using
Sun's MPxIO facility. While this is great for reliability, it results in the
/dev/dsk device IDs changing from cXtYd0 to something virtually unreadable like
"c4t5000C5000B21AC63d0s3".
Since the entries in /dev/{rdsk,d
