evms-gui: EVMS - GUI Frontend ---------------------------------------------------------------------- File: evms-gui-2.5.5-24.52.i586.rpm Patchrpm: evms-gui-2.5.5-24.52.i586.patch.rpm Version: 2.5.5-24.52 Size: 261 kB Patchsize: 261 kB Date: Tue 25 Sep 2007 0:7:54 CEST Source: evms-2.5.5-24.52.src.rpm Security: No ---------------------------------------------------------------------- Description: There is a window between DOS segment manager realizes a disk has Netware partitions and the disk is assigned to Netware segment manager. In such a window, data may be written to the wrong address and thus cause corruption. Bug description: Server Hardware x86 Sles10 sp1 aha29160 scsi with two Seagate 180 gig scsi drives Pool and volume is created and mounted without issues. When pool is deactivated, or server rebooted, pool fails to activate. The following is the error in iManager when "activate" button is clicked. Error: POOL: Cannot change state for this pool. Error Number: The pool is being disabled. I/O is not allowed. This is the output from NSS screen: Activating pool "POOL"... ** Pool layout v43.02 ** Previous clean shutdown detected (consistency check OK) ** Loading system objects Sep 6, 2007 8:47:29 am NSS-4.10a-1448: zfsVol[393] Unable to read ROOTDIR from the volume "POOL_IV_", status=20206. You may be out of memory. Run Verify. Sep 6, 2007 8:47:29 am NSS-4.10a-xxxx: comnPool[2504] Pool POOL: System data error 20012(purgeLog[652]). Block 44323975(file block -44323975)(ZID 4) Sep 6, 2007 8:47:29 am NSS-4.10a-1449: zlssLogicalVolume[4980] Error reading PoolData Block 44323974, status=20206. Sep 6, 2007 8:47:29 am NSS-4.10a-1449: zfsVolumeData[216] Error reading VolumeData Block 44323971, status=20206. Sep 6, 2007 8:47:29 am NSS-4.10a-1449: zlssLogicalVolume[4980] Error reading PoolData Block 44323974, status=20206. Sep 6, 2007 8:47:29 am NSS-4.10a-689: comnPool[402] Could not change pool POOL to the ACTIVE state. Status=20206 zio[1820]. Use 'NSS /ErrorCode=20206' to obtain more information. I have tried to create the pool with both drives in the same pool, or with each drive in it's own pool...get the same issue. This hardware config has a very long history with SLES9/Sles10. The drives work fine when used as ext3 or reiser.