From jon.bvincent@gmail.com Thu Apr 23 05:39:57 2009 Received: from wf-out-1314.google.com ([209.85.200.170]) by stoneboat.aleph1.co.uk with esmtp (Exim 4.69) (envelope-from ) id 1Lwqj1-0007ZI-Gi for yaffs@lists.aleph1.co.uk; Thu, 23 Apr 2009 05:39:56 +0100 Received: by wf-out-1314.google.com with SMTP id 24so289689wfg.23 for ; Wed, 22 Apr 2009 21:39:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=GH6WfvRFS3Ev8SAGxOrZo2iflvZ9KOz+xgZJqYPwhRI=; b=lhZlyBzwKiXDXM6Xp4eCO6F4wN5Mo5f3iyaKswqH4vgJinMBuvUvbAYa0420YF3Mrc LVIIUct8Mh8ivN2g+4rXegc6r4IL5J1JVyOZdqJYYZ6ZQSNBlMKj9kJmzvrKDWhMtKWk 1znNWao9JFfzMETMFztSe152SCkHsfU1PaPlc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=pzx8WeZkIopZGfFD879JzZMd1mxKN5ZEakvLy4iUmND4NqZC7EN0skvPi4hLKQIXum m2R4yF53oQSKXQZeQ8AQii/oR2HAPreI9TNkP7XDrgg0IX5VDGkXhNi6gFaxM35Py7V9 X/4iS/PX5qtlhcUf5dxOlSMmU83yMgdFBng6w= MIME-Version: 1.0 Received: by 10.142.239.11 with SMTP id m11mr195068wfh.120.1240461590122; Wed, 22 Apr 2009 21:39:50 -0700 (PDT) Date: Thu, 23 Apr 2009 10:09:50 +0530 Message-ID: <26bd38970904222139p314d3a0cxcea9cac18602c770@mail.gmail.com> From: Jon Vincent To: yaffs@lists.aleph1.co.uk Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 209.85.200.170 X-SA-Exim-Mail-From: jon.bvincent@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] Yaffs for 2.4.20 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: Thu, 23 Apr 2009 04:39:57 -0000 Hello, I'm using the yaffs from the CVS repository HEAD against 2.4.20 linux kernel. The filesystem while mounting has a problem in yaffs_write_super() function. This function is being called continuously and makes the kernel to freeze. After making the following change, i was able to mount the fs but the reads/writes are not consistent. diff a/yaffs_fs.c b/yaffs_fs.c static void yaffs_MarkSuperBlockDirty(void *vsb) { struct super_block *sb = (struct super_block *)vsb; T(YAFFS_TRACE_OS, ("yaffs_MarkSuperBlockDirty() sb = %p\n", sb)); -// if (sb) -// sb->s_dirt = 1; + if (sb) + sb->s_dirt = 1; } For instance, when a file is created and a few bytes are written followed by a sync, it gets checkpointed. But the file name is not showing up when 'ls' is used. Moreover, at times the file names are corrupted. An unmount/remount reveals that the file indeed does not gets stored. Im also trying to understand the design of the FS/GC handling part so i could use the latest YAFFS from CVS in 2.4+ kernels. It would be great help if someone could provide directions to where the problem could be? Or a pointer to latest YAFFS release for 2.4 kernels would also be helpful. Regards, Jon