From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752277AbZHXPDh (ORCPT ); Mon, 24 Aug 2009 11:03:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751309AbZHXPDg (ORCPT ); Mon, 24 Aug 2009 11:03:36 -0400 Received: from smtp.nokia.com ([192.100.122.233]:62274 "EHLO mgw-mx06.nokia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750748AbZHXPDf (ORCPT ); Mon, 24 Aug 2009 11:03:35 -0400 Message-ID: <4A92A9F9.10706@gmail.com> Date: Mon, 24 Aug 2009 17:55:53 +0300 From: Artem Bityutskiy User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3 MIME-Version: 1.0 To: Theodore Tso CC: Florian Weimer , Pavel Machek , Goswin von Brederlow , Rob Landley , kernel list , Andrew Morton , mtk.manpages@gmail.com, rdunlap@xenotime.net, linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org Subject: Re: [patch] ext2/3: document conditions when reliable operation is possible References: <20090312092114.GC6949@elf.ucw.cz> <200903121413.04434.rob@landley.net> <20090316122847.GI2405@elf.ucw.cz> <200903161426.24904.rob@landley.net> <20090323104525.GA17969@elf.ucw.cz> <87ljqn82zc.fsf@frosties.localdomain> <20090824093143.GD25591@elf.ucw.cz> <82k50tjw7u.fsf@mid.bfk.de> <20090824130125.GG23677@mit.edu> In-Reply-To: <20090824130125.GG23677@mit.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 24 Aug 2009 14:56:06.0021 (UTC) FILETIME=[01C63B50:01CA24CB] X-Nokia-AV: Clean Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Theodore, thanks for the insightful writing. On 08/24/2009 04:01 PM, Theodore Tso wrote: ...snip ... > It's for this reason that I've never been completely sure how useful > Pavel's proposed treatise about file systems expectations really are > --- because all storage subsystems *usually* provide these guarantees, > but it is the very rare storage system that *always* provides these > guarantees. There is a thing called eMMC (embedded MMC) in the embedded world. You may consider it as a non-removable MMC. This thing is a block device from the Linux POW, and you may mount ext3 on top of it. And people do this. The device seems to have a decent FTL, and does not look bad. However, there are subtle things which mortals never think about. In case of eMMC - power cuts may make some sectors unreadable - eMMC returns ECC errors on reads. Namely, the sectors which were being written at the very moment when the power cut happened may become unreadable. And this makes ext3 refuse mounting the file-system, this makes chkfs.ext3 refuse the file-system. Although this should be fixable in SW, but we did not find time to do this so far. Anyway, my point is that documenting subtle things like this is a very good thing to do, just because nowadays we are trying to use existing software with flash-based storage devices, which may violate these subtle assumptions, or introduce other ones. Probably, Pavel did too good job in generalizing things, and it could be better to make a doc about HDD vs SSD or HDD vs Flash-based-storage. Not sure. But the idea to document subtle FS assumption is good, IMO. -- Best Regards, Artem Bityutskiy (Артём Битюцкий)