SCIENTIFIC-LINUX-USERS Archives

August 2019

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: XFS memory allocation deadlock
From:
Pat Riehecky <[log in to unmask]>
Reply To:
Pat Riehecky <[log in to unmask]>
Date:
Thu, 22 Aug 2019 08:20:38 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines) 
I believe the solution is two fold:

- The SL 7.7 kernel will help prevent the problem from reoccurring 
(currently in sl-testing, scheduled for release Monday)
- Existing fragmentation should probably be cleaned up via xfs_fsr[1]

Pat

[1] 
https://blog.codecentric.de/en/2017/04/xfs-possible-memory-allocation-deadlock-kmem_alloc/

On 8/21/19 8:10 PM, Bill Maidment wrote:
> Hi
> During copying a large file (about 200GB) to a backup hard drive, I am 
> getting a multitude of XFS possible memory allocation deadlock messages.
> RedHat Portal shows the following:
>
> XFS issues "possible memory allocation deadlock in kmem_alloc" messages
> Solution Verified - Updated August 9 2019 at 2:51 AM - English
> Issue
>
>     Seeing file system access issues on XFS based file systems.
>     dmesg shows continuous entries with:
>
>     XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
>
> Does anyone know what the solution is? And if SL7 will get this 
> solution soon?
>

-- 
Pat Riehecky

Fermi National Accelerator Laboratory
www.fnal.gov
www.scientificlinux.org

ATOM RSS1 RSS2