LUNs that have been added to the file-based storage group are discovered during the normal storage discovery (diskmark) and mapped to their corresponding storage pools on the VNX for file. If a pool is encountered with the same name as an existing user-defined pool or system-defined pool from the same VNX for block system, diskmark will fail. It is possible to have duplicate pool names on different VNX for block systems, but not on the same VNX for block system.
For VNX for file, a storage pool cannot contain both mirrored and non-mirrored LUNs. If diskmark discovers both mirrored and non-mirrored LUNs, diskmark will fail. Also, data may be unavailable or lost during failovers.
The array is pretty much out of the box, no previous configuration existed, so the first thing that was created was via the Disk Provisioning for File Wizard.
It created RG 8,9,10,11, and within each RG, two luns. Nothing was previously present.
I ran the server_log server_2 command, whose output was pretty large, and noticed a large re-occurence of the following message:-
Thanks for the comprehensive replies guys. In the end I shut down the whole array, and restarted block/file. Upon completion, the errrors had gone, and the diskmark process had completed, resulting in the creation of the Storage pool for file.
o17Uu33DCF12520
4 Operator
•
1.1K Posts
0
January 8th, 2014 19:00
LUNs that have been added to the file-based storage group are discovered during the normal storage discovery (diskmark) and mapped to their corresponding storage pools on the VNX for file. If a pool is encountered with the same name as an existing user-defined pool or system-defined pool from the same VNX for block system, diskmark will fail. It is possible to have duplicate pool names on different VNX for block systems, but not on the same VNX for block system.
For VNX for file, a storage pool cannot contain both mirrored and non-mirrored LUNs. If diskmark discovers both mirrored and non-mirrored LUNs, diskmark will fail. Also, data may be unavailable or lost during failovers.
Rainer_EMC
4 Operator
•
8.6K Posts
0
January 9th, 2014 03:00
server_log server_2 should show the specific diskmark error
topcat021
11 Posts
0
January 9th, 2014 13:00
Thanks Guys,
The array is pretty much out of the box, no previous configuration existed, so the first thing that was created was via the Disk Provisioning for File Wizard.
It created RG 8,9,10,11, and within each RG, two luns. Nothing was previously present.
I ran the server_log server_2 command, whose output was pretty large, and noticed a large re-occurence of the following message:-
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l00 rwStatus 0, DMStatus
2, mtype 8, marker 1, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
46136960, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l01 rwStatus 0, DMStatus
2, mtype 8, marker 2, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
23068288, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l02 rwStatus 0, DMStatus
2, mtype 8, marker 3, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
4193920, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l03 rwStatus 0, DMStatus
2, mtype 8, marker 4, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
4193920, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l04 rwStatus 0, DMStatus
2, mtype 8, marker 5, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
8388224, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l05 rwStatus 0, DMStatus
2, mtype 8, marker 6, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
134217344, DMLoc 0
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 12, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l6 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l6, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 13, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l7 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l7, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 14, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l8 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l8, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 15, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l9 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l9, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 16, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l10 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l10, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 17, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l11 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l11, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l00 rwStatus 0, DMStatus
2, mtype 8, marker 1, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
46136960, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l01 rwStatus 0, DMStatus
2, mtype 8, marker 2, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
23068288, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l02 rwStatus 0, DMStatus
2, mtype 8, marker 3, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
4193920, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l03 rwStatus 0, DMStatus
2, mtype 8, marker 4, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
4193920, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l04 rwStatus 0, DMStatus
2, mtype 8, marker 5, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
8388224, DMLoc 0
2014-01-09 10:19:51: STORAGE: 6: rwDiskMark: Read c00t00l05 rwStatus 0, DMStatus
2, mtype 8, marker 6, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
134217344, DMLoc 0
There are a large number of the following messages too:-
2014-01-09 11:34:06: STORAGE: 3: cdb: 2a 00 00 00 41 bf 00 00 28 00 00 00
2014-01-09 11:34:06: STORAGE: 6: rwDiskMark: Read c00t00l04 rwStatus 0, DMStatus
2, mtype 8, marker 5, savedSBlock 0, savedDCap 0, allowGrow FALSE, diskMLoc
8388224, DMLoc 0
2014-01-09 11:34:06: STORAGE: 3: Failover succeeded: c0t0l4 irp 0x010ecc2608.
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l0
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l1
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l2
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l3
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l4
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l5
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l0
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l1
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l2
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l3
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l4
2014-01-09 11:34:18: ADMIN: 6: Command succeeded: camtrespass c0t0l5
2014-01-09 11:34:48: CAM: 6: Scan All Buses
2014-01-09 11:36:48: ADMIN: 6: Can't close stream:refcount 1
Pool:MACExec BLOCKED for 21149 seconds: Server operations may be impacted .
2014-01-09 18:50:01: KERNEL: 3: 3: ThreadsServicesSupervisor: Service:MAC
Is it time to log a call?
o17Uu33DCF12520
4 Operator
•
1.1K Posts
0
January 9th, 2014 18:00
look at this:
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l6, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 13, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l7 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l7, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 14, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l8 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l8, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 15, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l9 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l9, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 16, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l10 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l10, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
2014-01-09 10:19:51: STORAGE: 3: ClariionVolume::getDiskCapacity: failed, volume
Basic-Volume 17, TUR returned CamStatus 0x84, 0x5/0x25/0x0
2014-01-09 10:19:51: STORAGE: 4: Physical device at c0t1l11 has been disconnected
2014-01-09 10:19:51: STORAGE: 3: scsicfg_check_drive: Volume c0t1l11, device has
been deleted or changed, path rescan failed, cannot read/write drive mark
It appears to me that the volume configuration on block layer has not yet been what was presented to the file layer.
It's time to verify the existence and configuration of those LUNs on both layers.
topcat021
11 Posts
0
January 14th, 2014 13:00
Hi All,
Thanks for the comprehensive replies guys. In the end I shut down the whole array, and restarted block/file. Upon completion, the errrors had gone, and the diskmark process had completed, resulting in the creation of the Storage pool for file.
This can be closed now.
TC