> On 02/28/11 22:39, Dave Pooser wrote: > > On 2/28/11 4:23 PM, "Garrett D'Amore" <garr...@nexenta.com> > wrote: > > > >> Drives are ordered in the order they are *enumerated* when they *first* > >> show up in the system. *Ever*. > > > > Is the same true of controllers? That is, will c12 remain c12 or > > /pci@0,0/pci8086,340c@5 remain /pci@0,0/pci8086,340c@5 even if other > > controllers are active?
Well, it will so long as the contents of /etc/path_to_inst, /dev/cfg, and /dev/[r]dsk remain untouched. If one is feeling intrepid (or annoyed that the SATA boot drives you want to be c0 are showing up as c4 because the USB controllers are getting enumerated first), one can modify this. For SAS controllers, selectively nuking the contents of /dev/dsk/cX, renaming /dev/cfg/cX to /dev/cfg/cY, updating the archive, and rebooting -r works rather well. For ICH10s, I've discovered that if one writes a for-loop that renames /dev/[r]dsk/c1t0d0s0 -> c0t0d0s0 while otherwise cleansing out unwanted entries, the devfsadm reconfig process honors the naming implied by existing symlinks and re-numbers the USB controllers accordingly. Do *not* try this at ... well, actually, try it at home long before you try this on your production box, as this is also a very good way to make your machine completely unbootable - and I wouldn't mention that you're doing this to anyone at S.uh.Oracle... (Maybe there's an easier way. I don't know it, though.) -bacon who is incredibly bugged by the idea of the boot drive being anything BUT c0t0d0s0.... _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
