All of lore.kernel.org
 help / color / mirror / Atom feed
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 14:27:36 +0100	[thread overview]
Message-ID: <24015049.MUjmLyMSVC@blindfold> (raw)
In-Reply-To: <df8dc8e7-cb9a-4cef-bca6-cfc40092b1d1@colorfullife.com>

Manfred,

Am Freitag, 1. Dezember 2017, 08:41:28 CET schrieb Manfred Spraul:
> >> Image after that command:
> >> https://sourceforge.net/projects/calculix-rpm/files/ubifs/image-168169.bi
> >> n/d ownload
> > 
> > Which file contains the MTD with chk_fs being enabled?
> 
> I'm not sure if this help, it only adds more data that will confuse:
> The image.bin is obviously identical, I have only enabled chk_fs for the
> replay.
> 
> And: The mount was done using 4.14, the image was created using 4.14-rc5.
> If you want: Here is the data (dmesg output + images)
> https://sourceforge.net/projects/calculix-rpm/files/ubifs/chkfs_4.14/

I still don't get which Image is the right one.
I gave image-168167.bin a try, but it contains many errors, I'm not sure
if it contains the first error.

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. :-)

Thanks,
//richard

  parent reply	other threads:[~2017-12-05 13:27 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 [this message]
2017-12-05 19:11                             ` Manfred Spraul
2017-12-05 20:06                               ` Richard Weinberger
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=24015049.MUjmLyMSVC@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.