From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from a.ns.miles-group.at ([95.130.255.143] helo=radon.swed.at) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Y0osu-0004kl-0c for linux-mtd@lists.infradead.org; Tue, 16 Dec 2014 09:57:40 +0000 Message-ID: <549001FC.10008@nod.at> Date: Tue, 16 Dec 2014 10:57:16 +0100 From: Richard Weinberger MIME-Version: 1.0 To: hujianyang Subject: Re: [PATCH] UBI: add ubi_err() to report the failure of leb read References: <548FE51D.60707@huawei.com> <548FE72D.5040803@huawei.com> <548FF98E.5000503@nod.at> <549000C1.4090709@huawei.com> In-Reply-To: <549000C1.4090709@huawei.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: linux-mtd , Artem Bityutskiy List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Am 16.12.2014 um 10:52 schrieb hujianyang: > On 2014/12/16 17:21, Richard Weinberger wrote: >> Am 16.12.2014 um 09:02 schrieb hujianyang: >>> Hi, >>> >>> I met a problem that I was failed to mount a UBIFS partition. >>> >>> [ 38.442770] UBI error: ubi_io_read: error -74 (ECC error) while reading 26624 bytes from PEB 54:104448, read 26624 bytes >>> [ 38.852461] UBI error: ubi_io_read: error -74 (ECC error) while reading 77824 bytes from PEB 346:53248, read 77824 bytes >>> [ 38.864142] UBIFS error (pid 1444): ubifs_recover_leb: corruption -3 >>> [ 38.870487] UBIFS error (pid 1444): ubifs_scanned_corruption: corruption at LEB 928:55280 >>> [ 38.878625] UBIFS error (pid 1444): ubifs_scanned_corruption: first 8192 bytes from LEB 928:55280 >>> [ 38.892117] UBIFS error (pid 1444): ubifs_recover_leb: LEB 928 scanning failed >>> mount: mounting ubi1:bak on /HFFS2: failed: Structure needs cleaning >>> >>> I think it is caused by an ECC error of nand flash. Do we have some methods >>> to mount this partition? Data losing is acceptable. >> >> I don't think that UBIFS has such a mount option. > > Er, I don't know it either. How about a mount option like --force? Then every single embedded vendor will use this flag to keep the broken MTD/UBI/UBIFS setups running as long as possible no mater of how corrupted the data is. :-) IIRC UBIFS will either mount and work correctly as expected or fail hard. >> You can dump the raw data and inspect the corrupted data. >> Maybe you can fix it by hand. > > Yes, I want a try~! If we have to introduce a new feature or new mount > option. So would you like to help me? Do you think it's a valuable > work? I'm not a fan of such a mount option. What we really need is a fsck.ubifs and a ubifs dump tool to fix and recover broken UBIFS images. Thanks, //richard