From Scott.Wagner@us.bosch.com Tue Mar 18 13:12:46 2008
Received: from smtp2-v.fe.bosch.de ([139.15.237.6])
	by stoneboat.aleph1.co.uk with esmtp (Exim 4.63)
	(envelope-from <Scott.Wagner@us.bosch.com>) id 1JbbcD-0008I3-Ud
	for yaffs@lists.aleph1.co.uk; Tue, 18 Mar 2008 13:12:45 +0000
Received: from vsmta2.fe.internet.bosch.com (unknown [10.4.98.30])
	by imta8.fe.bosch.de (Postfix) with ESMTP id 6FE483C016
	for <yaffs@lists.aleph1.co.uk>; Tue, 18 Mar 2008 14:12:20 +0100 (CET)
Received: from mta2.sbd.internet.bosch.com (vsgw2.fe.internet.bosch.com
	[10.4.98.13])
	by vsmta2.fe.internet.bosch.com (Postfix) with ESMTP id CDEE0800B0
	for <yaffs@lists.aleph1.co.uk>; Tue, 18 Mar 2008 14:12:19 +0100 (CET)
Received: from sbdimc01.us.bosch.com (sbdimc01.us.bosch.com [10.24.248.73])
	by mta2.sbd.internet.bosch.com (Postfix) with ESMTP id D551DA0014
	for <yaffs@lists.aleph1.co.uk>; Tue, 18 Mar 2008 09:12:18 -0400 (EDT)
Received: from sbdmail14.us.bosch.com ([10.24.248.72]) by
	sbdimc01.us.bosch.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 18 Mar 2008 09:12:18 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 18 Mar 2008 09:12:17 -0400
Message-ID: <24F9B61D2FEAB94BBA5930904B9A79270793051B@sbdmail14.us.bosch.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Index: AciI+bBRZwdCixUDR8OPPdq/Y2LRjQ==
From: "Wagner Scott (ST-IN/ENG1.1)" <Scott.Wagner@us.bosch.com>
To: <yaffs@lists.aleph1.co.uk>
X-OriginalArrivalTime: 18 Mar 2008 13:12:18.0771 (UTC)
	FILETIME=[B1964A30:01C888F9]
X-SA-Exim-Connect-IP: 139.15.237.6
X-SA-Exim-Mail-From: Scott.Wagner@us.bosch.com
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on
	stoneboat.aleph1.co.uk
X-Spam-Level: 
X-Spam-Status: No, score=-3.7 required=5.0 tests=AWL, BAYES_00, MISSING_SUBJECT,
	RCVD_IN_DNSWL_MED autolearn=ham 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] (no subject)
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: Tue, 18 Mar 2008 13:12:46 -0000

Hi all,

I have been using YAFFS successfully with my Cirrus EP9302 / ST
NAND512W3A /Linux 2.6.14 embedded system for about a year now.  Nice
work!!!

I am writing to ask for recommendations / suggestions for safing the
YAFFS, its underlying MTD, and the NAND Flash at power failure.  To date
I have not had any file system corruption attributable to power fail
during write, but I would like to "make sure."  I receive a Power Fail
interrupt about 100 mS before my processor is reset.  What, if any,
steps can I take to safe YAFFS and flush pending writes when I receive
the power fail interrupt?

Thanks

Scott Wagner



