AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080806182736.413be9b8@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<amit.bothra@onstor.com>,<jobi.ariyamannil@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E0B31A5BE@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 6 Aug 2008 18:27:42 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Amit Bothra" <amit.bothra@onstor.com>
Cc: "Jobi Ariyamannil" <jobi.ariyamannil@onstor.com>
Subject: Re: status for the corruption bugs
Message-ID: <20080806182742.496362dd@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0B31A5BE@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0B31A5BE@onstor-exch02.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: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Thanks, Amit.  Can you give me an idea what the current plan of attack
is?

Thanks,

a


On Wed, 6 Aug 2008 18:25:19 -0700 "Amit Bothra"
<amit.bothra@onstor.com> wrote:

> TED00025036 - The corruption here is to the inode file and its missing
> emaps for two blocks. After going through all the evidence we had for
> this defect, it seems to point that the bug is somewhere in the
> copy-on-write mechanism for inode file blocks during snapshot
> operations. I went through that code today and could not find any
> holes yet.
> 
> TED00025037 - The corruption here is to the refcount file. My
> assumption (based on evidence and code review) is that the
> corruptions were initially on the snapbit file of a snapshot and when
> that snapshot was removed it caused corruption in the refcount file.
> I have coded a fix that would prevent a corrupt snapbit file
> corrupting the refcount file, but we still need to figure out how the
> snapbit file was corrupted in the first place.
> 
> TED00025042 - Here again the corruption is to the emap of the inode
> file. I did not get time to investigate this yet. This can be related
> to TED00025036.
> 
> Thanks,
> Amit
