From: Edward Shishkin <edward.shishkin@gmail.com>
To: "Mathieu Bélanger" <b747xx@gmail.com>,
"Metztli Information Technology"
<jose@huitzilopochtli.metztli-it.com>
Cc: ReiserFS development mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: reiser4[StorageManager(2383)]: lzo1_alloc
Date: Fri, 25 Aug 2017 18:22:05 +0200 [thread overview]
Message-ID: <9cff1013-fc3c-ea1b-8fd4-6f0ca0c0c698@gmail.com> (raw)
In-Reply-To: <CAMDqdwxyR7nFy66chkkfVCRVHKA_PHoTosMrynXvvRRiDB-q7Q@mail.gmail.com>
As a possible fixup we can leave data uncompressed.
I think it is rather rare event (the flood of warnings is because
of inability to allocate workspace for the same chunk of data.
Edward.
On 08/25/2017 06:49 AM, Mathieu Bélanger wrote:
> I did have that bug specifically with Chromium too, I did initial try
> to test by disabling ALSR (I was suspecting the Ryzen silicon bug that
> finally can be RMA).
> But disabling ALSR caused more problem so ...
>
> I did "fix" the issue by recompiling Chromium with -O2 instead of -O3.
>
> And I do have similar problem with Firefox 57 compiled with -O3 (Again
> -O2 fix it and Firefox 55 with -O3 is not affected)
>
> On Thu, Aug 24, 2017 at 11:42 PM, Metztli Information Technology
> <jose@huitzilopochtli.metztli-it.com
> <mailto:jose@huitzilopochtli.metztli-it.com>> wrote:
>
>
>
> On Thu, Aug 24, 2017 at 6:01 AM, Edward Shishkin
> <edward.shishkin@gmail.com <mailto:edward.shishkin@gmail.com>> wrote:
> > So, memory allocation policy got changed in the upstream,
> > and we need to perform pre-allocation to not fail at flush time.
> > I am sorry, but right now I don't have a time for this..
> No worries, sir. I simply fulfilled your request for feedback.
>
> Background for this test was to evaluate 2TB maximum slice allowed
> by Google Compute Engine in cloud instances, specifically Debian
> with transparent compression reiser4.
>
> Currently, (default) transparent compression reiser4 formatting is
> not available[1] in my custom Debian-Installer (d-i) but planned
> to make available in a future implementation.
>
> >
> >
> > On 08/24/2017 06:59 AM, Metztli Information Technology wrote:
> >>
> >> Much appreciated, Ed-
> >>
> >> Noticed improvement, notwithstanding...
> >>
> >> Context:
> >>
> >> uname -a
> >> Linux huitzilopochtli 4.12.0-1+reiser4.0.1-amd64 #1 SMP Debian
> >> 4.12.6-3+reiser4.0.1 (2017-08-14) x86_64 GNU/Linux
> >>
> >> (I have reinstalled same kernel two times after patching so the
> above
> >> string retained the older original kernel installation date.
> >> but
> >> uname -v
> >> #1 SMP Debian 4.12.6-3...[means upgrade '-3' reflects fact that
> I rebuilt
> >> fs with your latest two(2) patches to address the issue.])
> >>
> >>
> >> ls -ltc /lib/modules/4.12.0-1*64/kernel
> >> total 18
> >> drwxr-xr-x 14 root root 16 Aug 23 02:14 sound/
> >> drwxr-xr-x 5 root root 24 Aug 23 02:13 lib/
> >> drwxr-xr-x 2 root root 4 Aug 23 02:13 mm/
> >> drwxr-xr-x 60 root root 62 Aug 23 02:13 fs/
> >> drwxr-xr-x 3 root root 73 Aug 23 02:13 crypto/
> >> drwxr-xr-x 2 root root 4 Aug 23 02:13 block/alloc workspace
> >> drwxr-xr-x 51 root root 51 Aug 18 17:02 net/
> >> drwxr-xr-x 3 root root 3 Aug 18 17:02 virt/
> >> drwxr-xr-x 70 root root 70 Aug 18 17:02 drivers/
> >> drwxr-xr-x 3 root root 3 Aug 18 17:02 arch/
> >>
> >> After applying (fs/) patches and rebooting, I began to apply
> load to the
> >> machine where with previous kernel I had already built
> GCC-5-branch and
> >> Apache OpenOffice. Memory is limited to 16Gb RAM; copy
> operations were
> >> started from 1TB USB disk to local reiser4 transparent
> compression, a 16Gb
> >> data copy to same local filesystem, began a 2Gb svn download,
> etc.; I had
> >> Firefox open with several tabs open and launched chromium
> browser -- which
> >> began producing relevant feedback. I have set a two(2) thousand
> lines limit
> >> output in my shell so that is the reason *all* of the below
> WARNINGS repeat
> >> that number of times.
> >>
> >> Chromium browser launched but app did not open in the GUI and
> got stuck
> >> with un-killable processes (memory starvation?):
> >>
> >> % kill -9 $(pgrep chromium)
> >> % pgrep chromium
> >> 6320
> >> 6743
> >> 6814
> >> 7050
> >>
> >> Subsequently dmesg showed (<process number>) none necessarily
> in the order
> >> below as dmesg alternated in producing sequence:
> >>
> >> [ 6175.145234] reiser4[chromium(7050)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 6175.145248] reiser4[chromium(7050)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 6175.145261] reiser4[chromium(7050)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 6175.145275] reiser4[chromium(7050)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> (snip)
> >>
> >> [ 7116.052780] reiser4[TaskSchedulerBa(6793)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7116.053021] reiser4[TaskSchedulerBa(6793)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7116.053044] reiser4[TaskSchedulerBa(6793)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7116.055925] reiser4[TaskSchedulerBa(6793)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> (snip)
> >>
> >> [ 7309.117294] reiser4[Chrome_DBThread(6796)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7309.117305] reiser4[Chrome_DBThread(6796)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7309.117316] reiser4[Chrome_DBThread(6796)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7309.117327] reiser4[Chrome_DBThread(6796)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7309.117338] reiser4[Chrome_DBThread(6796)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> (snip)
> >>
> >> [ 7550.849425] reiser4[Chrome_HistoryT(6828)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7550.849436] reiser4[Chrome_HistoryT(6828)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7550.849446] reiser4[Chrome_HistoryT(6828)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >>
> >> [ 7550.849457] reiser4[Chrome_HistoryT(6828)]: lzo1_alloc
> >>
> (/usr/src/build/kernel/build/linux/fs/reiser4/plugin/compress/compress.c:241)[edward-878]:
> >> WARNING: alloc workspace for lzo1 (tfm action =
> 1) failed
> >> (snip)
> >>
> >>
> >> On Tue, Aug 22, 2017 at 11:49 AM, Edward Shishkin
> >> <edward.shishkin@gmail.com <mailto:edward.shishkin@gmail.com>>
> wrote:
> >>>
> >>> Hello,
> >>>
> >>> Please, try the attached patches.
> >>> The first patch improves responsiveness to vm subsystem
> >>> (modified version of ->migratepage() from Ivan Shapovalov).
> >>> The second patch performs memory allocation in the critical
> >>> place with __GFP_NOFAIL flag.
> >>> Let us know about results.
> >>>
> >>> Thanks,
> >>> Edward.
> >>
> >> []
> >>>>
> >>>> 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]
> >>
> >> This time dmesg did not output any references to
> [StorageManager(<pid>)]
> >>
> >>
> [1] but default reiser4 formatting can be performed from the
> command line in another virtual terminal.
>
> Best Professional Regards.
>
> --
> Jose R R
> http://metztli.it
> ---------------------------------------------------------------------------------------------
> Download Metztli Reiser4: Debian Stretch with Linux 4.12
> ---------------------------------------------------------------------------------------------
> for AMD64 https://sf.net/projects/metztli-reiser4/
> <https://sf.net/projects/metztli-reiser4/>
> ---------------------------------------------------------------------------------------------
> Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
> ---------------------------------------------------------------------------------------------
> from our GitHub http://Nepohualtzintzin.com repository. Cloud the
> easy way!
> --
> To unsubscribe from this list: send the line "unsubscribe
> reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> <http://vger.kernel.org/majordomo-info.html>
>
>
next prev parent reply other threads:[~2017-08-25 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 4:42 reiser4[StorageManager(2383)]: lzo1_alloc Metztli Information Technology
[not found] ` <CAMDqdwxyR7nFy66chkkfVCRVHKA_PHoTosMrynXvvRRiDB-q7Q@mail.gmail.com>
2017-08-25 16:22 ` Edward Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-26 7:15 Metztli Information Technology
2017-08-28 13:15 ` Edward Shishkin
2017-08-24 4:59 Metztli Information Technology
2017-08-24 13:01 ` Edward Shishkin
2017-08-20 17:15 Metztli Information Technology
2017-08-22 18:49 ` Edward Shishkin
2017-08-30 9:29 ` 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=9cff1013-fc3c-ea1b-8fd4-6f0ca0c0c698@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=b747xx@gmail.com \
--cc=jose@huitzilopochtli.metztli-it.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).