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: Sun, 12 Nov 2017 20:54:03 +0100 [thread overview]
Message-ID: <5883680.7ftK6mdJzr@blindfold> (raw)
In-Reply-To: <195075f7-01f8-58d2-ba1c-4291e62a39cc@colorfullife.com>
Manfred,
Am Sonntag, 12. November 2017, 20:26:38 CET schrieb Manfred Spraul:
> Hello together,
>
> in a power fail stress test with ubifs, I ran into 5 images that do not
> mount:
>
> 3x ubifs_check_node() fails, called by ubifs_garbage_collect_leb()
> 2x UBIFS assert failed in ubifs_rcvry_gc_commit at 1219 (pid 9570)
> (and ~550 images with just asserts, the mount was successful)
>
> The test was done using kernel 4.14.0-rc5+ #105 SMP PREEMPT.
> The test involves create/rename/remove, using ecryptfs with xattr.
>
> Are these known issues?
Nope.
This should not happen at all. ;-(
> Are there any patches that I should apply?
No, 4.14 is recent.
> What would you need to analyze them?
Can you retry without encryptfs and xattr?
xattrs had already some issues, maybe there are more.
Just as a start to know where to start digging.
> If you need the image (~32 MB), I'll try to find a suitable server.
> Below is the dmesg output from mounting the first bad image.
An image would be good but I need one with the 1st generation error.
Can you please make sure the the UBIFS debugfs knob "chk_fs" is set?
If set, UBIFS will check the whole filesystem while mounting.
Thanks,
//richard
next prev parent reply other threads:[~2017-11-12 19:54 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 [this message]
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
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=5883680.7ftK6mdJzr@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.