A former colleague implemented FreeNAS on VMware. He provisioned several vDisks of identical size to the FreeNAS VM.
Then he created pools - one pool per vDisk.
At the OS level, I can use "zpool status" and "gpart list" commands, and this enables me to match zpools to the /dev/daxx devices that they use.
However, I need to figure out which VMware virtual disk correlates to each OS device /dev/daxx
If this were a CentOS machine, I would use the "dmesg" command and filter for useful messages. For example, on the following VM, I can see that vDisk 0 is sda, vDisk 1 is sdb and vDisk 2 is sdc. (But one cannot assume that the order of vDisks matches the order of VM OS disks)
I need to do something equivalent on our FreeNAS server so that I can tell which vDisk goes with which /dev/daxx device, so that I can safely remove the vDisk that corresponds to a deleted zpool. Can someone help?
Many Thanks,
Janet
Then he created pools - one pool per vDisk.
At the OS level, I can use "zpool status" and "gpart list" commands, and this enables me to match zpools to the /dev/daxx devices that they use.
However, I need to figure out which VMware virtual disk correlates to each OS device /dev/daxx
If this were a CentOS machine, I would use the "dmesg" command and filter for useful messages. For example, on the following VM, I can see that vDisk 0 is sda, vDisk 1 is sdb and vDisk 2 is sdc. (But one cannot assume that the order of vDisks matches the order of VM OS disks)
Code:
[jeinhorn@useitconfluence ~]$ dmesg | grep " sd " | grep logical [ 1.156251] sd 2:0:0:0: [sda] 104857600 512-byte logical blocks: (53.6 GB/50.0 GiB) [ 1.156407] sd 2:0:1:0: [sdb] 104857600 512-byte logical blocks: (53.6 GB/50.0 GiB) [ 1.156905] sd 2:0:2:0: [sdc] 629145600 512-byte logical blocks: (322 GB/300 GiB)
I need to do something equivalent on our FreeNAS server so that I can tell which vDisk goes with which /dev/daxx device, so that I can safely remove the vDisk that corresponds to a deleted zpool. Can someone help?
Many Thanks,
Janet