Environment
Novell Open Enterprise Server 2 (OES 2)
Linux
Situation
A pool has been expanded. The partition used to
extend the pool had been used on NetWare (6.0.x) before. When
checking with NSSMU, the partition is not visible.
When to pool is on a NCS resource, this resource will be comatose.
When performing an evms_activate an error on the screen appears that a part is missing. When you check the /var/log/evms-engine.log you will see the following error:
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: examining object mpathh_mbr
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: device name
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: examining object mpathh1
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: device name mpathh1
Jul 31 20:51:17 bcc1-cl1-n02 _2_ 2b7726c1a6d0 NWSegMgr: get_mm_disk_private_data: error: get_mm_disk_private_data(mpathh1) returning NULL
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: created segment mpathh1.meta1 on disk mpathh1 start= 0 size = 790273982640
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: created segment mpathh1.1 on disk mpathh1 start= 790273982640 size = -790273974512
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: Called activate on mpathh1.1
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: created segment mpathh1.meta2 on disk mpathh1 start= 8128 size = 32
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: created segment mpathh1.2 on disk mpathh1 start= 8160 size = 212119168
Jul 31 20:51:17 bcc1-cl1-n02 _2_ 2b7726c1a6d0 NWSegMgr: insert_mm_segment_into_ordered_list: error, insertion failed ... RC= 22
Jul 31 20:51:17 bcc1-cl1-n02 _2_ 2b7726c1a6d0 NWSegMgr: build_segments: error 22 inserting meta segment mpathh1.meta2
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: Discovery, Failure ... not my disk or no partitions
When to pool is on a NCS resource, this resource will be comatose.
When performing an evms_activate an error on the screen appears that a part is missing. When you check the /var/log/evms-engine.log you will see the following error:
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: examining object mpathh_mbr
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: device name
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: examining object mpathh1
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: device name mpathh1
Jul 31 20:51:17 bcc1-cl1-n02 _2_ 2b7726c1a6d0 NWSegMgr: get_mm_disk_private_data: error: get_mm_disk_private_data(mpathh1) returning NULL
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: created segment mpathh1.meta1 on disk mpathh1 start= 0 size = 790273982640
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: created segment mpathh1.1 on disk mpathh1 start= 790273982640 size = -790273974512
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: Called activate on mpathh1.1
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: created segment mpathh1.meta2 on disk mpathh1 start= 8128 size = 32
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: created segment mpathh1.2 on disk mpathh1 start= 8160 size = 212119168
Jul 31 20:51:17 bcc1-cl1-n02 _2_ 2b7726c1a6d0 NWSegMgr: insert_mm_segment_into_ordered_list: error, insertion failed ... RC= 22
Jul 31 20:51:17 bcc1-cl1-n02 _2_ 2b7726c1a6d0 NWSegMgr: build_segments: error 22 inserting meta segment mpathh1.meta2
Jul 31 20:51:17 bcc1-cl1-n02 _5_ 2b7726c1a6d0 NWSegMgr: Discovery, Failure ... not my disk or no partitions
Resolution
This issue has been resolved in EVMS patches release 27 January 2010 or later for SLES10 SP2 and SLES10 SP3.
There is one other possible cause. When the disk has been used as another file system (e.g. EXT3, NTFS) before, the signature add the end is containing false information. This will also prevent EVMS from recognizing this new partition as a NSS partition. novell-nss-4.11.2734-0.4.1 or higher will remove this signature when performing a init with NSSMU on this disk. If the problem still persist, or an older NSS is on the server please contact Novell Technical Services. They will be able to resolve this problem
There is one other possible cause. When the disk has been used as another file system (e.g. EXT3, NTFS) before, the signature add the end is containing false information. This will also prevent EVMS from recognizing this new partition as a NSS partition. novell-nss-4.11.2734-0.4.1 or higher will remove this signature when performing a init with NSSMU on this disk. If the problem still persist, or an older NSS is on the server please contact Novell Technical Services. They will be able to resolve this problem