From dkovar@gmail.com Sun Apr 19 02:46:15 2009 Received: from yx-out-1718.google.com ([74.125.44.154]) by stoneboat.aleph1.co.uk with esmtp (Exim 4.69) (envelope-from ) id 1LvM6k-0000Gf-9z for yaffs@lists.aleph1.co.uk; Sun, 19 Apr 2009 02:46:15 +0100 Received: by yx-out-1718.google.com with SMTP id 4so210174yxp.80 for ; Sat, 18 Apr 2009 18:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:x-pgp-universal :message-id:from:to:mime-version:subject:date:x-mailer:content-type :content-transfer-encoding; bh=yYaeqbjHyOjSHPMxg6YRKD/FEIPsyOYU8a+E8bJMlMo=; b=TSHh7AHx3yN1RfwUHWFDALvsiHepQ95X4z3ddjW0oVQcH/fo3bmShopN1eKCgo7Mqr dhR0DAau7OKwiFcszd7M3/jz5kCjGlcl3Kz069ua9B4PGHAS9cJ40u2pVg5wAp7BUmwh 6yb6SUHHiXiaekyymvguXP/diETs6WxRH6c9E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-pgp-universal:message-id:from:to:mime-version:subject:date :x-mailer:content-type:content-transfer-encoding; b=JypfuV4Au6VcvIerlC16INLzNbUiQsdi+eqSJ24XOF7j+5fOQ4hqHTdM0sQHh86JQp FYJF6NQp1bz4qQrdzDeZ5Ac61e4lA6tXoHHtniPYF+0U7PZ/Nw++uFOz3WQJC7XPHdCX Gq+nOSJI1kV2K2FXSU6FxRG8Xn2bU9ehBg/Fc= Received: by 10.90.69.15 with SMTP id r15mr5296835aga.17.1240105569246; Sat, 18 Apr 2009 18:46:09 -0700 (PDT) Received: from amber-2.local (pool-71-113-133-34.frstil.dsl-w.verizon.net [71.113.133.34]) by mx.google.com with ESMTPS id 40sm7541009aga.48.2009.04.18.18.46.05 (version=SSLv3 cipher=OTHER); Sat, 18 Apr 2009 18:46:06 -0700 (PDT) Received: from [127.0.0.1] by amber-2.local (PGP Universal service); Sat, 18 Apr 2009 20:46:05 -0500 X-PGP-Universal: processed; by amber-2.local on Sat, 18 Apr 2009 20:46:05 -0500 Message-Id: From: David Kovar To: yaffs@lists.aleph1.co.uk Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sat, 18 Apr 2009 20:45:53 -0500 X-Mailer: Apple Mail (2.930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 74.125.44.154 X-SA-Exim-Mail-From: dkovar@gmail.com X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Subject: [Yaffs] Unable to mount system.img but unyaffs reads it correctly. X-BeenThere: yaffs@lists.aleph1.co.uk X-Mailman-Version: 2.1.11 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2009 01:46:16 -0000 Good evening, I'm trying to mount yaffs2 image files on a Linux system. I've got a kernel compiled correctly and can successfully mount an file containing a yaffs2 filesystem but only lost+found is present in the mount point. A lot of reading suggests this is due to missing OOB data. However, the same thing happens with the system.img file from the Google SDK. Further, unyaffs successfully reads system.img and unpacks it so all the necessary information is present in the image file to read the filesystem. Any ideas on why unyaffs recognizes the filesystem and the yaffs2 kernel code doesn't? -David