From: mannu on 18 Feb 2010 09:40 Hello, For EFI labelled disk, the full disk is not represented by s2 slice but by only disk name like "cXtYdZ". I am facing a problem where in the EFI full disk entry "cXtYdZ" is not at all getting created for an EFI labelled disk. I tried "devfsadm" and also reconfiguration reboot but with no success. Please help on this. solaris (x86 and sparc) support only 7 slices (s0 - s6) for EFI, but strangely, on some systems, I see entries for s7, s8 too. These systems also do not have entry for full EFI disk. It is observed on these systems that slice s7 has the major and minor same as the EFI disk. Is s7 slice the full EFI disk in this case? As per man page, api "efi_alloc_and_read()" from libefi.so, returns the slice index as return value when it is called with file descriptor that has opened slice. For eg: if we open slice s4 and give the file descriptor as arguement to "efi_alloc_and_read()", it returns 4. But if we open full EFI disk (provided the entry cXtYdZ is indeed created in "/dev/dsk"), and give this file descriptor to "efi_alloc_and_read()", it gives the return value as 7 always. (regardless of s7 being present or not). Please help on this. Thanks and Regards, Manish Singh.
From: mannu on 18 Feb 2010 09:45 On Feb 18, 7:40 pm, mannu <manishsingh...(a)gmail.com> wrote: > Hello, > > For EFI labelled disk, the full disk is not represented by s2 slice > but by only disk name like "cXtYdZ". > I am facing a problem where in the EFI full disk entry "cXtYdZ" is not > at all getting created for > an EFI labelled disk. > I tried "devfsadm" and also reconfiguration reboot but with no > success. > Please help on this. > > solaris (x86 and sparc) support only 7 slices (s0 - s6) for EFI, but > strangely, on some systems, > I see entries for s7, s8 too. These systems also do not have entry for > full EFI disk. > It is observed on these systems that slice s7 has the major and minor > same as the EFI disk. > Is s7 slice the full EFI disk in this case? > > As per man page, api "efi_alloc_and_read()" from libefi.so, > returns the slice index as return value when it is called with file > descriptor that has opened slice. > For eg: if we open slice s4 and give the file descriptor as arguement > to "efi_alloc_and_read()", > it returns 4. > > But if we open full EFI disk (provided the entry cXtYdZ is indeed > created in "/dev/dsk"), > and give this file descriptor to "efi_alloc_and_read()", it gives the > return value as 7 always. > (regardless of s7 being present or not). > > Please help on this. > > Thanks and Regards, > Manish Singh. Also one more issue is that emc power path is installed on system. From emc clarion array, a lun is visible from 2 paths, and the lun is EFI labelled. system has created cXtYdZ entry in "/dev/dsk" for one path and not for other. EMC power path has also not created full disk psuedo name for this EFI labelled lun. For eg: EMC created "/dev/dsk/emcpower2a" "/dev/dsk/emcpower2b" .... .... .... "/dev/dsk/emcpower2h" but it has not created "/dev/dsk/emcpower2". Please help on this.
|
Pages: 1 Prev: Newbie query about patch Next: Samba mount on Solaris 10. |