On 22/08/2019 11:20 pm, Pat Riehecky wrote:
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]
Thanks Pat and
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]
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"
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
On 27/06/2019 1:06 am, Denice Deatrich wrote:
On Wed, 26 Jun 2019, Bill Maidment wrote:
Hi friends
I have run into a problem in SL7.6 copying a large KVM guest lvm
snapshot
file using cp --sparse=always
I get flooded with the following message:
XFS: cp(12985) possible memory allocation
On Wed, 26 Jun 2019, Bill Maidment wrote:
> Hi friends
> I have run into a problem in SL7.6 copying a large KVM guest lvm snapshot
> file using cp --sparse=always
> I get flooded with the following message:
>
> XFS: cp(12985) possible memory allocation deadlock size 131088 in
> kmem_realloc
Hi friends
I have run into a problem in SL7.6 copying a large KVM guest lvm
snapshot file using cp --sparse=always
I get flooded with the following message:
XFS: cp(12985) possible memory allocation deadlock size 131088 in
kmem_realloc (mode:0x250)
The copy ends eventually, but it takes
