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: Wed, 15 Nov 2017 21:29:14 +0100 [thread overview]
Message-ID: <7598033.H8v47AZKNl@blindfold> (raw)
In-Reply-To: <4fafb954-2b57-1b7a-cfc9-85d379c0aa57@colorfullife.com>
Manfred,
Am Mittwoch, 15. November 2017, 21:04:14 CET schrieb Manfred Spraul:
> Hi,
>
> On 11/14/2017 07:49 PM, Manfred Spraul wrote:
> > Hi Richard,
> >
> > On 11/13/2017 10:06 PM, Richard Weinberger wrote:
> >> No, the image that contains the first logical error.
> >> UBIFS can mount even if there are many problems with the structure.
> >> Therefore I need you to enable chk_fs.
> >
> > Done - and I even found a 2nd instance where the image got bad:
> > https://sourceforge.net/projects/calculix-rpm/files/ubifs/chk_fs/
>
> Sorry for the self-reply, I did another test:
> I applied "ubifs: replay: Detect and kill orphaned xattrs", i.e.
> https://patchwork.ozlabs.org/patch/780667/.
I would be astonished if that patch would fix your issues, it is supposed
to fix a -ENOSPC problem.
> Finding 1: It does not help
> Finding 2: I get for some images lots of "UBIFS error (ubi0:0 pid
> 13670): ubifs_replay_journal: Expected ino node, got: 1/2/3"
1/2/3?
Is always "got 0xFF but expected something different"?
If so, it can be a problem with garbage collect.
> The last good image is e.g. 164908, the first image with such messages
> is 164909:
> https://sourceforge.net/projects/calculix-rpm/files/ubifs/kill_xattr/
>
> And, perhaps it helps to understand the issues:
> The stress test is parallel, i.e. 4 parallel bash scripts that do
> something like "touch a b c ;rm c; mv a b;".
Hmm, nothing fancy. No O_TMPFILE, no xattr, no encryption. :-(
I hope I'll find some time during the weekend to inspect your images.
Thanks,
//richard
next prev parent reply other threads:[~2017-11-15 20:29 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 [this message]
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
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=7598033.H8v47AZKNl@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