On Jan 29, 2008, at 2:46 PM, Dan Weinman wrote: > I am getting the following error when trying to use one particular > lun on a 6140 array. > > Jan 29 14:25:46 t2000 vds: [ID 137619 kern.info] > vd_setup_full_disk(): ldi_open_by_dev() returned errno 16 for slice 3 > Jan 29 14:25:46 t2000 vds: [ID 556514 kern.info] vds_add_vd(): > Failed to add vdisk ID 1
It seems like the lun you are failing on is open by some other application on the service domain and hence the EBUSY error. Are you running Veritas or some other application that probably has this device open ? Thanks -Narayan > I have no problems with any of the other 9 luns. The lun is useable > from solaris, as I can newfs and mount a file system on it, but > can't use it as a disk for a guest domain. > The bindings from the control and guest domain. volx and vdiskx are > the vds and vdisk in question. > > root at t2000 #ldm list-bindings > NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME > primary active -n-cv SP 8 4G 0.4% 4h 29m > > MAC > 00:14:4f:21:c1:94 > > VCPU > VID PID UTIL STRAND > 0 0 0.5% 100% > 1 1 0.2% 100% > 2 2 0.1% 100% > 3 3 0.0% 100% > 4 4 2.2% 100% > 5 5 0.1% 100% > 6 6 0.0% 100% > 7 7 0.0% 100% > > MAU > CPUSET > (0, 1, 2, 3) > (4, 5, 6, 7) > > MEMORY > RA PA SIZE > 0x8000000 0x8000000 4G > > VARIABLES > use-nvramrc?=true > > IO > DEVICE PSEUDONYM OPTIONS > pci at 780 bus_a > pci at 7c0 bus_b > > VDS > NAME VOLUME OPTIONS DEVICE > primary-vds0 vol1 /ldomsbootpool/ > ldoms/ldom1/ldom1.bootdisk > vol2 /ldomsbootpool/ > ldoms/ldom2/ldom1.bootdisk > vol3 /dev/zvol/rdsk/ > ldomsvolpool/vol1 > vol4 /dev/rdsk/ > c2t200700A0B82987C2d5s0 > vol5 /usr2/bootdisks/ > ldom1.bootdisk > vol6 /usr2/datadisks/ > ldom1.datadisk > volx /dev/dsk/ > c2t200700A0B82987C2d1s2 > CLIENT VOLUME > vdisk1 at ldom1 vol1 > vdisk3 at ldom1 vol3 > vdisk4 at ldom1 vol4 > vdisk5 at ldom1 vol5 > vdisk6 at ldom1 vol6 > vdiskx at ldomx volx > > VCC > NAME PORT-RANGE > primary-vcc0 5000-5100 > CLIENT PORT > ldom1 at ldom1 5000 > ldomx at ldomx 5001 > > VSW > NAME MAC NET-DEV DEVICE MODE > primary-vsw0 00:14:4f:21:c1:94 e1000g0 switch at 0 > prog,promisc > PEER MAC > vnet1 at ldom1 00:14:4f:fa:a3:31 > vnet1 at ldomx 00:14:4f:f8:50:54 > > VCONS > NAME SERVICE PORT > SP > > ------------------------------------------------------------------------------ > > NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME > ldomx bound ----- 5001 4 1920M > > MAC > 00:14:4f:f8:24:b3 > > VCPU > VID PID UTIL STRAND > 0 16 100% > 1 17 100% > 2 18 100% > 3 19 100% > > MEMORY > RA PA SIZE > 0x8000000 0x188000000 1920M > > NETWORK > NAME SERVICE DEVICE MAC > vnet1 primary-vsw0 at primary network at 0 > 00:14:4f:f8:50:54 > PEER MAC > primary-vsw0 at primary 00:14:4f:21:c1:94 > vnet1 at ldom1 00:14:4f:fa:a3:31 > > DISK > NAME VOLUME TOUT DEVICE SERVER > vdiskx volx at primary-vds0 disk at 0 primary > > VCONS > NAME SERVICE PORT > ldomx primary-vcc0 at primary 5001 > > The error happens when the bind-domain command is used. > -- > This message was posted from opensolaris.org > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
