Problem
In Storage Foundation Cluster File System (SFCFS) 6.2, JBOD devices may not be exported in a Flexible Shared Storage (FSS) because they may not have a unique identification, which can cause corruption. This article contains a procedure for adding a manual JBOD definition.
Error Message
The disk is not supported for FSS operations.
Solution
The device disk_2 is not able to be exported in FSS. It also fails the checkfss test.
# vxdisksetup -fi disk_2
# vxdisk -e list | grep disk_2
disk_2 auto:cdsdisk - - online c1t2d0s2 -
# vxdisk export disk_2
VxVM vxdisk ERROR V-5-1-531 Device disk_2:
export failed: Disk not supported for FSS operations
# vxddladm checkfss disk_2
VxVM vxddladm INFO V-5-1-18714 disk_2 is not a valid disk for FSS.
The device disk_2 is currently using the serial number 5000CCA350C3A96F.
# vxdisk -p -x LUN_SERIAL_NO list
disk_2DEVICE LUN_SERIAL_NO disk_2 5000CCA350C3A96F
To add a SCSI JBOD definition, we need to find a unique ID. In this example, the serial number is reported in SCSI inquiry data for this disk (offset 36 in page code 0x0). This can vary between vendors so you will have to find a unique method related to your devices.
# /etc/vx/diag.d/vxscsiinq -d /dev/rdsk/c1t2d0s2
Inquiry for /dev/rdsk/c1t2d0s2, evpd 0x0, page code 0x0
Peripheral Qualifier/Device Type : 0
Removable bit : 0
Device type modifier : 0
ISO Version : 0
ECMA Version : 0
ANSI Version : 5
AEN Capability : 0
Terminat I/O Capability : 0
Additional Length : 45
Relative Addressing : 0
32 bit I/O : 0
16 bit I/O : 0
Sync capabilities : 0
Linked command : 0
Command Queing : 1
Soft Reset : 0
Vendor id : ATA
Product id : HITACHI HDS7216S
Revision : AB8A
Serial Number : PVE301ZMR81RDM
/dev/rdsk/c1t2d0s2: Raw data size 74
Bytes: 0 - 7 0x00 0x00 0x05 0x12 0x45 0x00 0x00 0x02 ....E...
Bytes: 8 - 15 0x41 0x54 0x41 0x20 0x20 0x20 0x20 0x20 ATA
Bytes: 16 - 23 0x48 0x49 0x54 0x41 0x43 0x48 0x49 0x20 HITACHI
Bytes: 24 - 31 0x48 0x44 0x53 0x37 0x32 0x31 0x36 0x53 HDS7216S
Bytes: 32 - 39 0x41 0x42 0x38 0x41 0x50 0x56 0x45 0x33 AB8APVE3
Bytes: 40 - 47 0x30 0x31 0x5a 0x4d 0x52 0x38 0x31 0x52 01ZMR81R
Bytes: 48 - 55 0x44 0x4d 0x20 0x20 0x20 0x20 0x20 0x20 DM
Bytes: 56 - 63 0x00 0x00 0x00 0x77 0x1e 0xa0 0x03 0x00 ...w....
Bytes: 64 - 71 0x03 0x20 0x0b 0xfd 0x16 0x00 0x00 0x00 . ......
Bytes: 72 - 73 0x00 0x00
Now, add the JBOD definition. This will happen for all devices that meet the criteria. Then rescan the device tree
# vxddladm addjbod vid=ATA pid="HITACHI HDS7216S" serialnum=18/-1/36/14
# vxdisk scandisks
# vxdisk -e list
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
disk_4 auto:cdsdisk - - online c1t2d0s2 -
Since the JBOD definition has altered the UDID type to jbod, from scsi3_jbod, the disk appears as a new disk, disk_4.
The checkfss test now succeeds.
# vxddladm checkfss disk_4 VxVM vxddladm INFO V-5-1-18713 disk_4 is a valid disk for FSS.
Now the disk can be exported
# vxdisk export disk_4# vxdisk listDEVICE TYPE DISK GROUP STATUSdisk_0 auto:cdsdisk disk_0 testdg onlinedisk_4 auto:cdsdisk - - online exported
Consult the Storage Foundation Cluster File System - Administrator Guide for more information about FSS and exporting disks.
Applies To:
Storage Foundation Cluster File System (SFCFS) 6.2