From neversetsun@ustc.edu Wed Apr 02 03:58:00 2008
Received: from smtp.ustc.edu.cn ([202.38.64.16] helo=ustc.edu.cn)
	by stoneboat.aleph1.co.uk with smtp (Exim 4.63)
	(envelope-from <neversetsun@ustc.edu>) id 1JgtAa-00055E-LF
	for yaffs@lists.aleph1.co.uk; Wed, 02 Apr 2008 03:58:00 +0100
Received: (eyou send program); Wed, 02 Apr 2008 10:57:59 +0800
Message-ID: <407105079.08481@ustc.edu.cn>
X-EYOUMAIL-SMTPAUTH: shizheng@mail.ustc.edu.cn
Received: from unknown (HELO [127.0.0.1]) (202.38.79.82)
	by 202.38.64.8 with SMTP; Wed, 02 Apr 2008 10:57:59 +0800
Message-ID: <47F2F613.1040000@ustc.edu>
Date: Wed, 02 Apr 2008 10:57:23 +0800
From: shizheng <neversetsun@ustc.edu>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: yaffs@lists.aleph1.co.uk,
 Charles Manning <manningc2@actrix.gen.nz>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 202.38.64.16
X-SA-Exim-Mail-From: neversetsun@ustc.edu
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on
	stoneboat.aleph1.co.uk
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,
	MSGID_FROM_MTA_HEADER,SPF_HELO_PASS autolearn=no version=3.2.3
X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000)
X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk)
Subject: [Yaffs] yaffs_VerifyCollectedBlock report error
X-BeenThere: yaffs@lists.aleph1.co.uk
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of YAFFS NAND flash filesystem <yaffs.lists.aleph1.co.uk>
List-Unsubscribe: <http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs>, 
	<mailto:yaffs-request@lists.aleph1.co.uk?subject=unsubscribe>
List-Archive: <http://lists.aleph1.co.uk/lurker/list/yaffs.html>
List-Post: <mailto:yaffs@lists.aleph1.co.uk>
List-Help: <mailto:yaffs-request@lists.aleph1.co.uk?subject=help>
List-Subscribe: <http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs>,
	<mailto:yaffs-request@lists.aleph1.co.uk?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2008 02:58:00 -0000

Hi,
yaffs_VerifyCollectedBlock reported "Block xxx is in state 4 after gc,
should be erased".
State 4 means YAFFS_BLOCK_STATE_ALLOCATING, how would this happen?

My testing environment is linux 2.6.24.3:
|1. modprobe nandsim first_id_byte=0x20 second_id_byte=0xa2
third_id_byte=0x00 fourth_id_byte=0x15| - 64MiB, 2048 bytes page;
2. mount -t yaffs2 -o sync /dev/mtdblock0 /mnt/nand
3. Then I ran postmark under /mnt/nand.
The file size is between 512B and 10kB.
The file number is 2000.
The transactions is 100000.
There were totally 312MB read and 336MB written to flash.

Have anybody encountered the same question?

best wishes, shizheng


