Please don't do this as a rule, it makes for horrendous support issues and breaks a lot of health check tools.
>> Actually, you can use the existing name space for this. By default, >> ZFS uses /dev/dsk. But everything in /dev is a symlink. So you could >> setup your own space, say /dev/myknowndisks and use more descriptive >> names. You might need to hack on the startup service to not look at >> /dev, but that shouldn't be too hard. In other words, if the answer >> is "let the sysadmin do it" then it can be considered solved. The >> stretch goal is to make some sort of reasonable name service. At >> this point I'll note the the FC folks envisioned something like that, >> but never implemented it. >> >> # ramdiskadm -a BrownDiskWithWhiteHat 150m >> /dev/ramdisk/BrownDiskWithWhiteDot >> # zpool create zwimming /dev/ramdisk/BrownDiskWithWhiteDot >> # zpool status zwimming >> pool: zwimming >> state: ONLINE >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> zwimming ONLINE 0 0 0 >> /dev/ramdisk/BrownDiskWithWhiteDot ONLINE >> 0 0 0 >> >> errors: No known data errors >> # ls -l /dev/ramdisk/BrownDiskWithWhiteHat >> lrwxrwxrwx 1 root root 55 Sep 25 17:59 >> /dev/ramdisk/BrownDiskWithWhiteDot -> >> ../../devices/pseudo/[EMAIL PROTECTED]:BrownDiskWithWhiteDot >> # zpool export zwimming >> # mkdir /dev/whee >> # cd /dev/whee >> # ln -s >> ../../devices/pseudo/[EMAIL PROTECTED]:BrownDiskWithWhiteHat >> YellowDiskUnderPinkBox >> # zpool import -d /dev/whee zwimming >> # zpool status zwimming >> pool: zwimming >> state: ONLINE >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> zwimming ONLINE 0 0 0 >> /dev/whee/YellowDiskUnderPinkBox ONLINE 0 >> 0 0 >> >> errors: No known data errors >> >> >> -- richard >> >> But nobody would actually do this. If the process can't be condensed into a >> single step (e.g. a single command), people won't bother. >> >> Besides, who would take the chance that a 'boot -r' would keep their >> elaborate symbolic link tree intact? I wouldn't. >> >> I've learned that you can't count on anything in /dev remaining over 'boot >> -r', patches, driver updates, san events, etc. >> _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
