From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.nokia.com ([192.100.105.134] helo=mgw-mx09.nokia.com) by bombadil.infradead.org with esmtps (Exim 4.69 #1 (Red Hat Linux)) id 1LNpxP-0008DX-RN for linux-mtd@lists.infradead.org; Fri, 16 Jan 2009 14:46:03 +0000 Subject: Re: Problem with ubiformat From: Artem Bityutskiy To: Johan In-Reply-To: References: <1232105373.25068.25.camel@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" Date: Fri, 16 Jan 2009 16:46:16 +0200 Message-Id: <1232117176.25068.32.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: linux-mtd@lists.infradead.org Reply-To: dedekind@infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2009-01-16 at 15:36 +0100, Johan wrote: > This is my output of flash_eraseall, so it looks like the same > input/output error exist in flash_eraseall but it continues anyway. Yeah, ubiformat should not panic as well. I think it should ask the user whether to: a) continue b) stop c) mark the eraseblock as bad and continue Well, if the -f option is given, it should just continue. I'll add this to my TODO list and will do later. But you may easily implement this yorself and send a patch if you do not want to wait. -- Best regards, Artem Bityutskiy (Битюцкий Артём)