From: Richard Weinberger <richard@nod.at>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS does not mount after powerfail
Date: Tue, 05 Dec 2017 21:06:28 +0100 [thread overview]
Message-ID: <1695485.xO2l5BsRhR@blindfold> (raw)
In-Reply-To: <aa51fb6e-61c9-1133-b2cf-f931ee7e105a@colorfullife.com>
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
next prev parent reply other threads:[~2017-12-05 20:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 19:26 UBIFS does not mount after powerfail Manfred Spraul
2017-11-12 19:54 ` Richard Weinberger
2017-11-13 20:59 ` Manfred Spraul
2017-11-13 21:06 ` Richard Weinberger
2017-11-14 18:49 ` Manfred Spraul
2017-11-15 20:04 ` Manfred Spraul
2017-11-15 20:29 ` Richard Weinberger
2017-11-16 16:51 ` Manfred Spraul
2017-11-19 20:52 ` Richard Weinberger
2017-11-23 22:03 ` Manfred Spraul
2017-11-28 21:00 ` Richard Weinberger
2017-11-30 17:41 ` Manfred Spraul
2017-11-30 20:03 ` Richard Weinberger
2017-12-01 7:41 ` Manfred Spraul
2017-12-01 10:01 ` Richard Weinberger
2017-12-01 17:38 ` Manfred Spraul
2017-12-05 13:27 ` Richard Weinberger
2017-12-05 19:11 ` Manfred Spraul
2017-12-05 20:06 ` Richard Weinberger [this message]
2017-12-05 22:19 ` Richard Weinberger
2017-12-06 18:42 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1695485.xO2l5BsRhR@blindfold \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).