From: Edward Shishkin <edward.shishkin@gmail.com>
To: Reiserfs development mailing list <reiserfs-devel@vger.kernel.org>
Cc: Mathieu Belanger <admin@korinar.com>
Subject: Re: reiser4[StorageManager(2383)]: lzo1_alloc...
Date: Wed, 30 Aug 2017 11:29:36 +0200 [thread overview]
Message-ID: <4908fc4e-583f-1507-7184-901681dcd263@gmail.com> (raw)
In-Reply-To: <599C7CB1.6080408@gmail.com>
On 08/22/2017 08:49 PM, Edward Shishkin wrote:
> Hello,
>
> Please, try the attached patches.
> The first patch improves responsiveness to vm subsystem
> (modified version of ->migratepage()
Hi all,
I found that the first patch leads to system lockups after ~1 hour of
stress-testing.
This is a side effect of appearing of non-parsed jnodes in writeback
queues for some
reasons. So please, drop it for now..
Thanks,
Edward.
> The second patch performs memory allocation in the critical
> place with __GFP_NOFAIL flag.
> Let us know about results.
>
> Thanks,
> Edward.
>
> On 08/20/2017 07:15 PM, Metztli Information Technology wrote:
>> Niltze, Ed-
>>
>> Although I am using your latest Reiser4 patch for Linux kernel 4.12.x
>> on a test 1.2TB (transparent compression) reiser4 root fs, I have seen
>> dmesg generate the following in lesser version patches and in much
>> smaller partitions, i.e., 20Gb -- with transparent compression, too.
>>
>> Your input would be greatly appreciated:
>>
>> [ 3449.944653] reiser4[StorageManager(2383)]: lzo1_alloc
>> (/mnt/chiucuetetl/usr/src/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
>> WARNING: alloc workspace for lzo1 (tfm action = 1)
>> failed
>>
>> [ 3449.944674] reiser4[StorageManager(2383)]: lzo1_alloc
>> (/mnt/chiucuetetl/usr/src/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
>> WARNING: alloc workspace for lzo1 (tfm action = 1)
>> failed
>>
>> [ 3449.944694] reiser4[StorageManager(2383)]: lzo1_alloc
>> (/mnt/chiucuetetl/usr/src/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
>> WARNING: alloc workspace for lzo1 (tfm action = 1)
>> failed
>>
>> [ 3449.944715] reiser4[StorageManager(2383)]: lzo1_alloc
>> (/mnt/chiucuetetl/usr/src/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
>> WARNING: alloc workspace for lzo1 (tfm action = 1)
>> failed
>>
>> [snip]
>> ( the above replicate for about two(2) thousand lines )
>>
>> Please note that the error above is not immediate but is triggered
>> possibly by multiple events run simultaneously, i.e.,
>> plugged 1TB USB hard disk with multiple partitions where copy
>> operation to local disk is being run; another copy operation to-from
>> local hard
>> disk itself on same filesystem; installing additional packages,
>> building local software, etc.
>>
>> Subsequently system slows down in latency and fan use increases in
>> all instances.
>>
>> Thank you in advance for your insight.
>>
>>
>> Best Professional Regards.
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> reiserfs-devel" in
>> the body of a message tomajordomo@vger.kernel.org
>> More majordomo info athttp://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-08-30 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 17:15 reiser4[StorageManager(2383)]: lzo1_alloc Metztli Information Technology
2017-08-22 18:49 ` Edward Shishkin
2017-08-30 9:29 ` Edward Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-24 4:59 Metztli Information Technology
2017-08-24 13:01 ` Edward Shishkin
2017-08-25 4:42 Metztli Information Technology
[not found] ` <CAMDqdwxyR7nFy66chkkfVCRVHKA_PHoTosMrynXvvRRiDB-q7Q@mail.gmail.com>
2017-08-25 16:22 ` Edward Shishkin
2017-08-26 7:15 Metztli Information Technology
2017-08-28 13:15 ` Edward Shishkin
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=4908fc4e-583f-1507-7184-901681dcd263@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=admin@korinar.com \
--cc=reiserfs-devel@vger.kernel.org \
/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).