From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from co202.xi-lite.net ([149.6.83.202]) by canuck.infradead.org with esmtp (Exim 4.72 #1 (Red Hat Linux)) id 1P8yZA-0008LU-Ky for linux-mtd@lists.infradead.org; Thu, 21 Oct 2010 17:04:38 +0000 Message-ID: <4CC0729B.7060109@parrot.com> Date: Thu, 21 Oct 2010 19:04:27 +0200 From: Matthieu CASTET MIME-Version: 1.0 To: "dedekind1@gmail.com" Subject: Re: ubifs: sync() causes writes even if nothing is changed References: <20101013163005.GB1889@silverbox.local> <1287581218.9272.67.camel@localhost> <4CBFF865.9010706@linutronix.de> <1287649931.2932.3.camel@localhost> In-Reply-To: <1287649931.2932.3.camel@localhost> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit Cc: linux-mtd , Adrian Hunter List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, Artem Bityutskiy a écrit : > On Thu, 2010-10-21 at 10:23 +0200, Sebastian Andrzej Siewior wrote: >> Artem Bityutskiy wrote: >>>> From a quick glance at the ubifs code, this might come out of the >>>> garbage collector that is triggered on every sync() and writes >>>> something even if nothing has changed. > > Yeah, the UBIFS must be writing the commit start and commit end nodes, > and then erasing the previous log LEB (all this is done in log.c). As > soon as I have time I'll look at this, I really do not have time right > now. And there is Matthiew's problem which is actually quite big, but > for some reasons affects only him :-) It could be interesting to know which nand flash are tested. On our boards ST 256MB chip work fine, but micron flash got unstable page problem (sorry I don't have the model number ATM). And it is getting worse, new SLC flash can now get up to 4 bits error per 512. Matthieu