AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080806154624.07b04833@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<dl-CougarCore@onstor.com>,<bob.miller@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 6 Aug 2008 15:49:07 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: dl-Cougar Core Team <dl-CougarCore@onstor.com>
Cc: Bob Miller <bob.miller@onstor.com>
Subject: [Cougar] Product Developement bug status
Message-ID: <20080806154907.7c169135@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=MP_pAi5BdFcD0fOrcD1USEKubP

--MP_pAi5BdFcD0fOrcD1USEKubP
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Summary:

Additional code has been checked in by Bill that is sort of like a
fix-to-a-fix of the fix for bug 24380 (checked in july 24th) and
buyg 25008 (checked in Monday).  It may address one or more of the
discovery/LUN issues currently plaguing us.

The bad news: 3 filesystem corruption bugs have surfaced.  I have asked
that Amit and Jobi crack hard on these and try to bust them out.  It
appears to me to be a bungled lock somewhere for the first two.





--MP_pAi5BdFcD0fOrcD1USEKubP
Content-Type: text/plain; name=cougar-bugz.86
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=cougar-bugz.86

File System
===========
TED00025036|CSS : EEK errors g12r10-vs1-vol1 MISMATCH: inum126951296 free
	Inode file blocks (emaps) are incorrect
TED00025037|CSS : EEK reports error on g2r8-vs1-vol1, MISMATCH ON block number
	Inode file blocks (emaps) are incorrect - possible storage issue - IO
	errors in elog
TED00025042|S-Soak: EEK reports errors on g2r5-vs1-vol13   (I#1) emapleaf 2214
	Possible {full file system, volume exception, snapshot op} collision?

SCSI/FC
======
TED00024174|Several volume exceptions due to array issue
	This problem does not happen is the config is changed to having
	paths to both of the array controllers. However. It is still
	clear that a problem is here, and that problem is linked to
	TED00024380.
TED00024380|Lost access to array - disable/enable loop
	This was happening during testing with the LSI array with a single
	fibre path into the array. I do see an issue for device log in,
	and I am looking into this.
TED00024963|CSS Volume exception, buffer cache 100% busy
	Possible storage issue.  Investigation continuing.
TED00024974|S-Soak & CSS: luns not visible at spm level
	This may have been caused by the same issue that was caused by
	TED00025008.
TED00025009|Nexsan Controller Failover
	Investigating.


--MP_pAi5BdFcD0fOrcD1USEKubP--
