linux-kernel - Re: UBIFS recovery taking too long

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 10 Dec 2013 11:41:44 -0700
From:	David Mosberger-Tang <dmosberger@...il.com>
To:	Adrian Hunter <adrian.hunter@...el.com>
Cc:	Shuah Khan <shuahkhan@...il.com>, dedekind1@...il.com,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: UBIFS recovery taking too long

Adrian,

On Tue, Dec 10, 2013 at 12:25 AM, Adrian Hunter <adrian.hunter@...el.com> wrote:

> Slowness is probably caused by trying to make free space.  Was the file
> system very full?  A smaller journal might help.

That's possible.  We have not been able to reproduce the issue in
house but a customer had it happen on several devices in a row (3 or 4
of them, I believe).  I don't think we are very sensitive to how long
it takes we just need to know an upper bound on the recovery time.

> Probably the only way to determine worst-case recovery time is to test it.
> Worst case conditions are likely to be a full journal and a nearly full file
> system.

I have not found a lot of UBIFS stresstest tools or even tools to
display what state UBIFS is in.  Can you point me to something?  I
assume lots of small writes would fill up the journal?  We'd be very
happy to test this more but as things stands, it's very hard to tell
how full the filesystem even is (due to compression) and I'm not sure
how to check on the state of the journal.

> Ideally you want to capture a file system image that exhibits the slow
> behaviour, then you can enable debug messages and see what it is doing.

OK, the two devices we've seen this initially have been restored so we
can't find out from those.
However, the customer affected by this issue may have another device
or two they haven't sent
back yet.  We might be able to snapshot the root filesystem on one of those.

  --david

>>>
>>> Thanks,
>>>
>>>   --david
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>> the body of a message to majordomo@...r.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>> Please read the FAQ at  http://www.tux.org/lkml/
>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/