From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.sigma-star.at ([95.130.255.111]) by bombadil.infradead.org with esmtp (Exim 4.87 #1 (Red Hat Linux)) id 1eMJTw-0002SB-9K for linux-mtd@lists.infradead.org; Tue, 05 Dec 2017 20:06:22 +0000 From: Richard Weinberger To: Manfred Spraul Cc: linux-mtd@lists.infradead.org Subject: Re: UBIFS does not mount after powerfail Date: Tue, 05 Dec 2017 21:06:28 +0100 Message-ID: <1695485.xO2l5BsRhR@blindfold> In-Reply-To: References: <195075f7-01f8-58d2-ba1c-4291e62a39cc@colorfullife.com> <24015049.MUjmLyMSVC@blindfold> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Manfred, Am Dienstag, 5. Dezember 2017, 20:11:20 CET schrieb Manfred Spraul: > > So, which file do I need to download to get the image that contains the > > first error as detected by chk_fs? > > > > The mode of operation of your tool should be: > > 1. Mount UBIFS > > 2. Do various filesystem operations > > 3. Random power-cut (in software) > > 4. Dump the image to a file X > > 5. Set chk_fs to 1 > > 6. Mount it again > > 7. If mount succeeds, drop X, umount and goto 1 > > > > Else if, chk_fs finds a problem. Store file X. > > > > I want file X. :-) > > The tool is in release process, thus let's just wait a bit. > There is no "goto 1" in my flow. > > Part 1: (done 5x, i.e. with xattr, without xattr, ...) > > 0. create UBI image, create empty UBIFS image. > 1. Mount UBIFS > 2. Do various filesystem operations. > In the background, record nand operations and store it in a trace. > > Part 2: (done ~100.000 times) > 1. Create an image file X by replaying from the trace. > 2. Set chk_fs to 1 > 3. Mount the image > 7. If mount succeeds: ignore the file X > If mount fails: remember file X > > Thus every image is a first error. No image has seen multiple unclean > unmounts. Hmm, when does the power-cut occur in your setup? i.e image-168167.bin and image-168168.bin show different errors and none of them fails the chf_fs test. They fail because of other reasons. Thanks, //richard