Sun StorEdge[TM] T3/T3+: LUNs not reported via format

Asset ID:	1-72-1004748.1
Update Date:	2010-10-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1004748.1 : Sun StorEdge[TM] T3/T3+: LUNs not reported via format

Related Items


Sun Storage T3 Array

Related Categories


GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other

PreviouslyPublishedAs
206593

Symptoms
"format" command does not report newly created Sun StorEdge[TM} T3 volume(LUN)

Resolution
Lack of slicing on the "new" volume will prevent the LUN being mapped to a
port and therefore prevent it being reported via "format".

If volume is to be removed and recreated, remove slices then the volume.
Following this add the volume and then create slices.
For instance, to re-create a volume  called "v1":
unmount the volume
	# vol unmount v1
	
destroy the volume
	# vol remove v1
	
readd the volume
	# vol add v1 data u1d5-9 raid 0
	
Initialize volume
	# vol init v1
	
Enable volume slicing
	# sys enable_volslice
Confirm vol slicing is enabled (this shuls report "enable_volslice: on")
	# sys list
execute the " vol stat " command. Drive status must be "0", if not, run the
" vol init v1 sysarea " to correct the drive labels.
create required slices
	# volslice create [<slice_name> [-s <start>] -z <size> <vol_name>]
	
mount volume
	# vol mount v1
Check the following to confirm all is correct
* vol stat
* vol mode
* volslice list
* lun map list
* lun perm list

Additional Information
T3B on Firmware release 2.01.04

In the example below the T3B partner pair consists of two volumes v0 and v1
(v1 had been removed and recreated)
volume has been recreated using the following commands:
unmount the volume
	# vol unmount v1
	
destroy the volume
	# vol remove v1
	
readd the volume
	# vol add v1 data u1d5-9 raid 0
	
Initialize volume
	# vol init v1
After the above proceedure the newly created LUN (v1) was not reported via
"format"
v1 reported on T3
vol stat
v0            u1d1   u1d2   u1d3   u1d4   u1d5   u1d6   u1d7   u1d8   u1d9
mounted      0      0      0      0      0      0      0      0      0
v1            u2d1   u2d2   u2d3   u2d4   u2d5   u2d6   u2d7   u2d8   u2d9
mounted      0      0      0      0      0      0      0      0      0
vol list
volume         capacity     raid  data      standby
v0             236.058 GB   5     u1d1-8    u1d9
v1             236.058 GB   5     u2d1-8    u2d9
however v1 not reported in port listmap
port listmap
port   targetid   addr_type   lun   volume        owner   access
u1p1      1        hard        0    v0            u1      primary
u2p1      2        hard        0    v0            u1      failover
v1 also not reported in lun map list
Lun No         Slice No
---------------------------
0              0
---------------------------
** Total 1 entries **
The following is reported by "sys list"  Note: enable_volslice is on
blocksize          : 64k
cache              : auto
mirror             : auto
mp_support         : rw
naca               : off
rd_ahead           : on
recon_rate         : med
sys memsize        : 128 MBytes
cache memsize      : 1024 MBytes
enable_volslice    : on
fc_topology        : auto
volslice_list indicates that no slices have been created for the new volume v1
volslice list
Slice         Slice Num     Start Blk     Size Blks     Capacity      Volume
s0            0             0             495052544      236.058 GB   v0
-             -             0             495052544      236.058 GB   v1
Sliced volumes can be masked to support multiple operating systems
simultaneously.
For further information  regarding volume slicing and capability, LUN
masking and mapping, see the  Sun StorEdge T3+ Array Administrator's
Manual.(816-4770-10)

Product
Sun StorageTek T3 Array

T3A, T3B, format, slicing, LUN
Previously Published As
70950

Change History
Date: 2003-12-08
User Name: 81292
Action: Approved
Comment: KCCP Reviewed valid
Version: 0
Date: 2003-12-08

Attachments

This solution has no attachment