Hi Natalie,
I did some more digging and found the following. the add_drv smbsrv fails after
getting a ENXIO at open devinfo:
truss excerpt of add_drv smbsrv:
924: modctl(MODLOADDRVCONF, 0xFFFFFFFF, 0x0807C59C, 0x08079000, 0x08047D5C) =
0
924: open("/devices/pseudo/[EMAIL PROTECTED]:devinfo", O_RDONLY) = 5
924: ioctl(5, 0xDF81, 0x080477D0) Err#6 ENXIO
924: close(5) = 0
924: fstat64(2, 0x08046C40) = 0
924: d=0x04800000 i=449108556 m=0020620 l=1 u=500 g=7 rdev=0x00600
001
924: at = Mar 31 05:03:33 PDT 2008 [ 1206965013 ]
924: mt = Mar 31 05:03:36 PDT 2008 [ 1206965016 ]
924: ct = Mar 28 08:37:53 PDT 2008 [ 1206718673 ]
924: bsz=8192 blks=0 fs=dev
924: write(2, " d e v f s a d m", 8) = 8
924: write(2, " : ", 2) = 2
924: write(2, " d r i v e r f a i l e".., 25) = 25
924: write(2, " s m b s r v", 6) = 6
924: write(2, "\n", 1) = 1
924: fcntl(3, F_SETLK, 0x08047BDC) = 0
924: typ=F_UNLCK whence=SEEK_SET start=0 len=0 sys=57103 pid
=134713344
924: close(3) = 0
924: _exit(1)
921: waitid(P_PID, 924, 0x08047050, WEXITED|WTRAPPED) = 0
basically fails at devfsadm -i smbsrv. Digging further it seems ioctl returning
a ENXIO means the:
ENXIO The request and arg arguments are valid for this dev-
ice driver, but the service requested can not be per-
formed on this particular subdevice.
here's a truss of devfsadm -i smbsrv
927: close(5) = 0
927: modctl(MODLOADDRVCONF, 0xFFFFFFFF, 0x0807C59C, 0x08079000, 0x08047D5C) =
0
927: open("/devices/pseudo/[EMAIL PROTECTED]:devinfo", O_RDONLY) = 5
927: ioctl(5, 0xDF81, 0x080477D0) Err#6 ENXIO
927: close(5) = 0
927: fstat64(2, 0x08046C40) = 0
927: d=0x04800000 i=449108556 m=0020620 l=1 u=500 g=7 rdev=0x00600
001
927: at = Mar 31 05:03:52 PDT 2008 [ 1206965032 ]
927: mt = Mar 31 05:03:55 PDT 2008 [ 1206965035 ]
927: ct = Mar 28 08:37:53 PDT 2008 [ 1206718673 ]
927: bsz=8192 blks=0 fs=dev
927: write(2, " d e v f s a d m", 8) = 8
927: write(2, " : ", 2) = 2
927: write(2, " d r i v e r f a i l e".., 25) = 25
927: write(2, " s m b s r v", 6) = 6
927: write(2, "\n", 1) = 1
927: fcntl(3, F_SETLK, 0x08047BDC) = 0
927: typ=F_UNLCK whence=SEEK_SET start=0 len=0 sys=57103 pid
=134713344
927: close(3) = 0
What reasons would quantify an unsupported subdevice to get a ENXIO? Is this
subdevice smbsrv returning the unsupported request?
devinfo -i smbsrv
devinfo -p smbsrv
returns no such file or directory but that makes sense because there is no
/devices /pseudo/[EMAIL PROTECTED]:smbsrv character device.
Would devinfo fail because its a ramfs? And are there any work arounds?
thanks
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
